Triple
T13170622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat G.91 PAN |
E312964
|
entity |
| Predicate | firstFlightAsTypeFamily |
P87764
|
FINISHED |
| Object | 1956 (Fiat G.91 base type) |
—
|
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: 1956 (Fiat G.91 base type) | Statement: [Fiat G.91 PAN, firstFlightAsTypeFamily, 1956 (Fiat G.91 base type)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightAsTypeFamily Context triple: [Fiat G.91 PAN, firstFlightAsTypeFamily, 1956 (Fiat G.91 base type)]
-
A.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
B.
firstFlightOnType
chosen
Indicates that an entity represents the first flight event conducted with a particular aircraft type or model.
-
C.
firstJetFamilyModel
Indicates that the subject is the first aircraft model in a particular family or series of jet models.
-
D.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
E.
firstFlightPeriod
Indicates the time period during which an entity’s first flight or initial airborne operation took place.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.