Triple
T7488797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish–German border |
E176949
|
entity |
| Predicate | currentLineEstablished |
P76531
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Danish–German border, currentLineEstablished, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLineEstablished Context triple: [Danish–German border, currentLineEstablished, 1920]
-
A.
lineStatus
Indicates the current operational or functional state of a line or connection within a system.
-
B.
hasLineUnderConstruction
Indicates that a line (such as a route, track, or service line) associated with an entity is currently in the process of being built, upgraded, or otherwise under construction.
-
C.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
-
D.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
E.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
- F. None of above. chosen
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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55abcd481909e42ca857fe46cd1 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:43 p.m.