Triple
T29873550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos-Dumont No. 6 dirigible |
E758657
|
entity |
| Predicate | achievedClosedCircuitFlight |
P168206
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Santos-Dumont No. 6 dirigible, achievedClosedCircuitFlight, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedClosedCircuitFlight Context triple: [Santos-Dumont No. 6 dirigible, achievedClosedCircuitFlight, true]
-
A.
closedForFlightOperations
Indicates that a location, facility, or area is temporarily unavailable or prohibited for conducting flight operations.
-
B.
flightOverWater
Indicates that a flight’s route passes over a body of water.
-
C.
operatorDuringRecordFlight
Indicates that an operator is responsible for or engaged in operating a system or vehicle during the time a particular flight is being recorded.
-
D.
supportsVisualFlightRulesOperations
Indicates that an entity enables or accommodates operations conducted under Visual Flight Rules (VFR).
-
E.
operatesAircraftFor
Indicates that one entity pilots or controls an aircraft on behalf of, or in service to, another entity.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c7a4fc8190a980f9bc778a6043 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:54 p.m.