Triple
T28948275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simao |
E730937
|
entity |
| Predicate | teaTradeRoute |
P35626
|
FINISHED |
| Object | routes to Tibet |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: routes to Tibet | Statement: [Simao, teaTradeRoute, routes to Tibet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teaTradeRoute Context triple: [Simao, teaTradeRoute, routes to Tibet]
-
A.
includesTradeRoute
chosen
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
B.
teaBrand
Indicates that one entity is a brand or producer associated with a particular type or product line of tea for the other entity.
-
C.
teaProductionRegion
Indicates the region or area where tea is produced or cultivated.
-
D.
teaIndustryDevelopedUnder
Indicates that the tea industry grew, expanded, or was significantly shaped under the influence, control, or conditions provided by a particular authority, period, or context.
-
E.
tradeDestination
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65b8a9a6c819091b9ec4563704490 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:42 a.m.