Triple
T3276678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diyala River |
E68773
|
entity |
| Predicate | formsBoundary |
P39423
|
FINISHED |
| Object | Part of Iran–Iraq border |
—
|
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: Part of Iran–Iraq border | Statement: [Diyala River, formsBoundary, Part of Iran–Iraq border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBoundary Context triple: [Diyala River, formsBoundary, Part of Iran–Iraq border]
-
A.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
B.
boundaryBetween
chosen
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
D.
boundaryCurrentOf
Indicates that one entity represents the current or present form/state of a boundary that is associated with or derived from another entity.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0128f08819084644f3c8fda2596 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.