Triple
T29977779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos-Dumont 14-bis |
E761497
|
entity |
| Predicate | laterFlightDistance |
P197821
|
FINISHED |
| Object | 220 meters |
—
|
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: 220 meters | Statement: [Santos-Dumont 14-bis, laterFlightDistance, 220 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterFlightDistance Context triple: [Santos-Dumont 14-bis, laterFlightDistance, 220 meters]
-
A.
firstFlightDistance
Indicates the distance covered during an entity’s first recorded flight.
-
B.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
C.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
D.
laterFlightDate
Indicates that one flight’s date occurs after another flight’s date in time.
-
E.
historicFlightDistance
Indicates the total distance that was covered during a past or completed flight.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
| PDg | Predicate description generation | batch_69feafa0acd881908bb6c01635b5537a |
completed | May 9, 2026, 3:53 a.m. |
Created at: April 29, 2026, 6:34 p.m.