Triple
T11214685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Alcock |
E265403
|
entity |
| Predicate | flightEndDate |
P54379
|
FINISHED |
| Object | 1919-06-15 |
—
|
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: 1919-06-15 | Statement: [John Alcock, flightEndDate, 1919-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightEndDate Context triple: [John Alcock, flightEndDate, 1919-06-15]
-
A.
flightEndedAt
Indicates the time or location at which a flight concludes or reaches its final endpoint.
-
B.
notableFlightEndDate
chosen
Indicates the date on which a notable or significant flight concluded or reached its endpoint.
-
C.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
-
D.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
E.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.