Triple
T30026067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos-Dumont No. 1 |
E762882
|
entity |
| Predicate | locationOfEarlyFlights |
P108377
|
FINISHED |
| Object | Paris |
—
|
NE NERFINISHED |
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: Paris | Statement: [Santos-Dumont No. 1, locationOfEarlyFlights, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfEarlyFlights Context triple: [Santos-Dumont No. 1, locationOfEarlyFlights, Paris]
-
A.
allegedFirstFlightPlace
Indicates the location where an entity is claimed or reported to have made its first flight, without asserting that the claim is definitively true.
-
B.
firstFlightLaunchSite
Indicates the location where an entity’s first flight was launched.
-
C.
firstFlightLandingSite
Indicates the location where an aircraft or spacecraft completes its initial flight by landing.
-
D.
placeOfFirstPoweredFlight
chosen
Indicates the location where an entity achieved its first successful powered flight.
-
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.
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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 29, 2026, 6:48 p.m.