Triple
T26095067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flensburg Fjord |
E658238
|
entity |
| Predicate | westernEndCity |
P4246
|
FINISHED |
| Object | Flensburg |
—
|
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: Flensburg | Statement: [Flensburg Fjord, westernEndCity, Flensburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernEndCity Context triple: [Flensburg Fjord, westernEndCity, Flensburg]
-
A.
westRegionalCity
Indicates that a city is located in the western region of a specified larger geographic or administrative area.
-
B.
westernTerminusNear
chosen
Indicates that the western endpoint of one entity is located close to another entity.
-
C.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
-
D.
eastRegionalCity
Indicates that a city is located in the eastern region of a specified larger area or jurisdiction.
-
E.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60735fddc8190a21af7b48e45b9be |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:50 p.m.