Triple
T34273141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HS 125 Series 800 |
E879377
|
entity |
| Predicate | firstFlightApproximateDecade |
P62849
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [HS 125 Series 800, firstFlightApproximateDecade, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightApproximateDecade Context triple: [HS 125 Series 800, firstFlightApproximateDecade, 1980s]
-
A.
firstFlightPeriod
chosen
Indicates the time period during which an entity’s first flight or initial airborne operation took place.
-
B.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
C.
firstWinningFlightDate
Indicates the date on which the first successful or winning flight associated with the subject occurred.
-
D.
maidenFlightYear
Indicates the calendar year in which an aircraft or similar vehicle made its first-ever flight.
-
E.
firstPoweredFlightDate
Indicates the calendar date on which an entity (typically an aircraft or spacecraft) achieved its first powered flight.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.