Triple
T4700766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Love Field |
E104262
|
entity |
| Predicate | openedAsAirfield |
P53197
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Dallas Love Field, openedAsAirfield, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsAirfield Context triple: [Dallas Love Field, openedAsAirfield, 1917]
-
A.
openedAsCivilAirport
Indicates that a facility or location began operation specifically as a civil (non-military) airport.
-
B.
openedAsMunicipalAirport
Indicates that an airport was initially established and began operation as a municipal (city- or town-operated) airport.
-
C.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
D.
airfieldOpened
chosen
Indicates that an airfield began operations or was officially opened at a certain time.
-
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.
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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.