Triple
T9292132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icarus |
E223544
|
entity |
| Predicate | flightEndedAt |
P87464
|
FINISHED |
| Object | sea |
—
|
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: sea | Statement: [Icarus, flightEndedAt, sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightEndedAt Context triple: [Icarus, flightEndedAt, sea]
-
A.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
-
B.
notableFlightEndDate
Indicates the date on which a notable or significant flight concluded or reached its endpoint.
-
C.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
D.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
-
E.
landingTimeUTC
Indicates the exact time, expressed in Coordinated Universal Time (UTC), at which an entity (such as an aircraft or spacecraft) completes its landing.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0866ff608190a07afac4afd0ec09 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.