Triple
T30366176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India and Myanmar |
E772426
|
entity |
| Predicate | borderShapeFactor |
P196980
|
FINISHED |
| Object | historical trade routes |
—
|
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: historical trade routes | Statement: [India and Myanmar, borderShapeFactor, historical trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderShapeFactor Context triple: [India and Myanmar, borderShapeFactor, historical trade routes]
-
A.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
B.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
C.
borderTriangle
Indicates that one entity is a triangular region or shape that forms part of the boundary or border of another entity.
-
D.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
E.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
- F. None of above. chosen
Provenance (4 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
| PDg | Predicate description generation | batch_69fe72db8810819089e397961b8ead7a |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 29, 2026, 7:58 p.m.