Triple
T24337521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draco (river) |
E613419
|
entity |
| Predicate | passesThroughCountryModern |
P5248
|
FINISHED |
| Object | Syria |
—
|
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: Syria | Statement: [Draco (river), passesThroughCountryModern, Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesThroughCountryModern Context triple: [Draco (river), passesThroughCountryModern, Syria]
-
A.
passesThroughCountry
chosen
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
-
B.
passesThroughCapital
Indicates that a route, path, or trajectory goes through or intersects the capital city of a given region or country.
-
C.
flowsThroughTraditionalTerritoryOf
Indicates that something, typically a natural feature like a river or route, passes through the recognized traditional territory of a particular group or community.
-
D.
nearModernBorderWith
Indicates that one entity is located close to the present-day political or geographic border shared with another entity.
-
E.
homeCountryModern
Indicates that one entity is the modern-day country that serves as the home or origin country of the other entity.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293212a0881908da028e81d26247d |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.