Triple
T14681839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 129 Hindenburg |
E344805
|
entity |
| Predicate | hasMaidenFlightDate |
P28082
|
FINISHED |
| Object | 1936-03-04 |
—
|
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: 1936-03-04 | Statement: [LZ 129 Hindenburg, hasMaidenFlightDate, 1936-03-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaidenFlightDate Context triple: [LZ 129 Hindenburg, hasMaidenFlightDate, 1936-03-04]
-
A.
isMaidenFlightOf
Indicates that an event is the first-ever flight of a particular aircraft or spacecraft.
-
B.
firstFlownAt
chosen
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
-
C.
maidenFlightYear
Indicates the calendar year in which an aircraft or similar vehicle made its first-ever flight.
-
D.
allegedFirstFlightDate
Indicates the date on which an entity is claimed or reported (but not necessarily confirmed) to have made its first flight.
-
E.
performedFirstFlightWith
Indicates that one entity carried out its inaugural or maiden flight in conjunction with, or using, another entity.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.