Triple
T35045489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siraf |
E1011183
|
entity |
| Predicate | tradeRouteTo |
P85749
|
FINISHED |
| Object | Basra |
—
|
NE NERFINISHED |
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: Basra | Statement: [Siraf, tradeRouteTo, Basra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeRouteTo Context triple: [Siraf, tradeRouteTo, Basra]
-
A.
tradRoutes
chosen
Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
D.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
E.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78596dbd881908ac257a644fac731 |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.