Triple
T5820673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Flyer (1903) |
E129097
|
entity |
| Predicate | firstFlightDistance |
P67152
|
FINISHED |
| Object | 120 feet |
—
|
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: 120 feet | Statement: [Wright Flyer (1903), firstFlightDistance, 120 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightDistance Context triple: [Wright Flyer (1903), firstFlightDistance, 120 feet]
-
A.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
B.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
C.
firstFlownAt
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
-
D.
firstFlightPeriod
Indicates the time period during which an entity’s first flight or initial airborne operation took place.
-
E.
firstCommercialFlight
Indicates that the subject entity operated or was involved in the earliest commercial flight associated with the object entity (such as a route, aircraft type, or service).
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:53 p.m.