Triple
T33483529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schkeuditzer Kreuz |
E857544
|
entity |
| Predicate | openedAsAutobahnInterchange |
P150731
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Schkeuditzer Kreuz, openedAsAutobahnInterchange, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsAutobahnInterchange Context triple: [Schkeuditzer Kreuz, openedAsAutobahnInterchange, 20th century]
-
A.
openedAsMotorway
chosen
Indicates that a road segment was initially opened to traffic specifically as a motorway.
-
B.
openedAsTurnpike
Indicates that something was initially established or began operation as a toll road or turnpike.
-
C.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
D.
openedAsINDStation
Indicates that a location or facility began operation specifically as a station within the IND (Independent Subway System) network.
-
E.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:38 a.m.