Triple
T3329837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube Delta |
E70006
|
entity |
| Predicate | majorRiverBranch |
P25047
|
FINISHED |
| Object | Chilia branch |
—
|
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: Chilia branch | Statement: [Danube Delta, majorRiverBranch, Chilia branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRiverBranch Context triple: [Danube Delta, majorRiverBranch, Chilia branch]
-
A.
distributaryOf
chosen
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
B.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
C.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
D.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.