Triple
T35017185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aero Vodochody |
E1010083
|
entity |
| Predicate | L-29DelfinFirstFlight |
P182483
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Aero Vodochody, L-29DelfinFirstFlight, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: L-29DelfinFirstFlight Context triple: [Aero Vodochody, L-29DelfinFirstFlight, 1959]
-
A.
L-159ALCARole
Indicates that an entity plays the specific role labeled "L-159ALCA" in relation to another entity or context.
-
B.
firstSuccessfulFlightDesignation
Indicates the specific designation or identifier assigned to an aircraft or spacecraft for its first successful flight.
-
C.
performedFirstFlightWith
Indicates that one entity carried out its inaugural or maiden flight in conjunction with, or using, another entity.
-
D.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
-
E.
firstAircraftName
Indicates the name assigned to the first aircraft associated with a given entity or context.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.