Triple
T27796810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Hill |
E702133
|
entity |
| Predicate | airCrashDate |
P166461
|
FINISHED |
| Object | 27 February 1958 |
—
|
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: 27 February 1958 | Statement: [Winter Hill, airCrashDate, 27 February 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airCrashDate Context triple: [Winter Hill, airCrashDate, 27 February 1958]
-
A.
missionAccidentDate
Indicates the date on which an accident occurred during or in relation to a mission.
-
B.
aircraftAccidentYear
Indicates the calendar year in which an aircraft accident occurred.
-
C.
aircraftAgeAtAccident
Indicates the length of time that has elapsed between an aircraft’s manufacture (or initial service) date and the date of the accident.
-
D.
aircraftAccident
Indicates that an event involves an aircraft experiencing an accident, such as a crash, collision, or serious malfunction during operation.
-
E.
originAirportAtTimeOfCrash
Indicates the airport from which an aircraft departed at the specific time when the crash occurred.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 27, 2026, 5:31 p.m.