Triple
T35842902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Fravor |
E1036133
|
entity |
| Predicate | describedObjectSpeedAs |
P184108
|
FINISHED |
| Object | beyond known aircraft performance |
—
|
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: beyond known aircraft performance | Statement: [David Fravor, describedObjectSpeedAs, beyond known aircraft performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedObjectSpeedAs Context triple: [David Fravor, describedObjectSpeedAs, beyond known aircraft performance]
-
A.
speedDescribedAs
chosen
Indicates that one entity characterizes or labels the speed of another entity using a particular description or term.
-
B.
approximateOperatingSpeed
Indicates that one entity specifies or characterizes the estimated or typical operating speed of another entity, rather than an exact value.
-
C.
speed
Indicates the rate at which an entity moves or changes position over time.
-
D.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
E.
marketedSpeedName
Indicates the branded or advertised name used to describe the speed of a product or service.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:06 p.m.