Triple
T29648585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamu |
E756071
|
entity |
| Predicate | borderTradeRoute |
P35626
|
FINISHED |
| Object | Tamu–Moreh corridor |
—
|
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: Tamu–Moreh corridor | Statement: [Tamu, borderTradeRoute, Tamu–Moreh corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTradeRoute Context triple: [Tamu, borderTradeRoute, Tamu–Moreh corridor]
-
A.
borderTradeType
Indicates the specific category or nature of trade that occurs across a border between two regions or countries.
-
B.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
C.
includesTradeRoute
chosen
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
D.
borderTradeItems
Indicates trade items that are specifically exchanged or transported across a shared border between two regions or countries.
-
E.
borderTradeStatus
Indicates the current condition or level of activity of trade occurring across a shared border between two regions or countries.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 28, 2026, 6:51 p.m.