Triple
T37193567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube (southern border) |
E921529
|
entity |
| Predicate | borderFunctionOf |
P14046
|
FINISHED |
| Object | Teleorman County |
—
|
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: Teleorman County | Statement: [Danube (southern border), borderFunctionOf, Teleorman County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderFunctionOf Context triple: [Danube (southern border), borderFunctionOf, Teleorman County]
-
A.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
B.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
C.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
D.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
E.
borderOrigin
Indicates that one entity is the original source or starting point from which a border or boundary of another entity is defined or derived.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:15 p.m.