Triple
T6716411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orontes River |
E153279
|
entity |
| Predicate | politicalBorderRole |
P67824
|
FINISHED |
| Object | forms part of the border between Syria and Turkey |
—
|
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: forms part of the border between Syria and Turkey | Statement: [Orontes River, politicalBorderRole, forms part of the border between Syria and Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalBorderRole Context triple: [Orontes River, politicalBorderRole, forms part of the border between Syria and Turkey]
-
A.
borderRegionRole
chosen
Indicates a role or function that an entity has specifically in relation to a border region or border area.
-
B.
borderedPoliticalSpheres
Indicates that two political regions or jurisdictions share a common boundary.
-
C.
stateBorderLengthRole
Indicates that an entity plays a specific role in defining, measuring, or characterizing the length of a state’s border.
-
D.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
E.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d125db3c8190aad28919226a16da |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.