Triple
T34081682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izmail |
E874060
|
entity |
| Predicate | locatedOnCanalOrArm |
P110158
|
FINISHED |
| Object | Chilia branch of the Danube |
E340245
|
NE 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: Chilia branch of the Danube | Statement: [Izmail, locatedOnCanalOrArm, Chilia branch of the Danube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnCanalOrArm Context triple: [Izmail, locatedOnCanalOrArm, Chilia branch of the Danube]
-
A.
positionInCanal
Indicates that an entity occupies a specific location within a canal.
-
B.
nearbyCanal
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
C.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
D.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
-
E.
locatedOnTributaryOf
chosen
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
- F. None of above.
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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae562eec81909427d34bef1ba0c4 |
completed | June 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.