Triple
T17343332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF4590 |
E421118
|
entity |
| Predicate | originOfFlight |
P127110
|
FINISHED |
| Object | Paris to New York charter service |
—
|
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: Paris to New York charter service | Statement: [AF4590, originOfFlight, Paris to New York charter service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfFlight Context triple: [AF4590, originOfFlight, Paris to New York charter service]
-
A.
wingOrigin
Indicates the anatomical source or structural region from which a wing arises or is derived.
-
B.
placeOfFirstPoweredFlight
Indicates the location where an entity achieved its first successful powered flight.
-
C.
poweredFlight
Indicates that an entity moves through the air using an onboard propulsion system that provides sustained thrust, rather than gliding or falling unpowered.
-
D.
usedAircraftOrigin
Indicates the place or source from which a used aircraft was originally obtained or came.
-
E.
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.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a18aca88190a816da85dd5fe371 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.