Triple
T1453835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbul Airport |
E31352
|
entity |
| Predicate | fullTransferOfFlightsDate |
P28779
|
FINISHED |
| Object | 2019-04-06 |
—
|
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: 2019-04-06 | Statement: [Istanbul Airport, fullTransferOfFlightsDate, 2019-04-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullTransferOfFlightsDate Context triple: [Istanbul Airport, fullTransferOfFlightsDate, 2019-04-06]
-
A.
winningFlightDate
Indicates the date on which the associated flight is determined to be the winning or selected one among a set of candidate flights.
-
B.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
C.
firstCompleteTransitBy
Indicates the agent (such as a person, vehicle, or mission) that first successfully completed a full transit or passage through a specified route, medium, or region.
-
D.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
-
E.
expeditionDepartureDate
Indicates the date on which an expedition is scheduled to or actually does depart.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57e82d48190a30a4512f39f5de0 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.