Triple
T31406532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karun-1 Dam |
E801143
|
entity |
| Predicate | isBuiltAcross |
P166011
|
FINISHED |
| Object | Karun River |
—
|
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: Karun River | Statement: [Karun-1 Dam, isBuiltAcross, Karun River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBuiltAcross Context triple: [Karun-1 Dam, isBuiltAcross, Karun River]
-
A.
builtAcross
chosen
Indicates that one entity is constructed so that it spans from one side of another entity to the other side, crossing over or covering it.
-
B.
builtAcrossStreetFrom
Indicates that one structure was constructed on the opposite side of a street directly facing another structure.
-
C.
isBuildingOf
Indicates that one entity is a building that belongs to, houses, or is associated with another entity (such as an organization, institution, or complex).
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:32 p.m.