Triple
T10950924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg S-Bahn line S1 |
E258722
|
entity |
| Predicate | openedAirportBranch |
P96798
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Hamburg S-Bahn line S1, openedAirportBranch, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAirportBranch Context triple: [Hamburg S-Bahn line S1, openedAirportBranch, 2008]
-
A.
airportOpened
Indicates that an airport began operations or was officially opened at a specific time.
-
B.
openedAsCivilAirport
Indicates that a facility or location began operation specifically as a civil (non-military) airport.
-
C.
openedAsMainAirport
Indicates that an airport was inaugurated or began operation specifically in the role of the primary or principal airport for a given city or region.
-
D.
openedAsMunicipalAirport
Indicates that an airport was initially established and began operation as a municipal (city- or town-operated) airport.
-
E.
openedAsInternationalAirport
Indicates that an airport was inaugurated or began operations specifically as an international airport, serving international flights from its opening.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fc156c8190826e124c13ce7242 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.