Triple
T32623242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bremen transatlantic flight |
E833985
|
entity |
| Predicate | takeoffTime |
P127109
|
FINISHED |
| Object | 1928-04-12T05:38:00Z |
—
|
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: 1928-04-12T05:38:00Z | Statement: [Bremen transatlantic flight, takeoffTime, 1928-04-12T05:38:00Z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffTime Context triple: [Bremen transatlantic flight, takeoffTime, 1928-04-12T05:38:00Z]
-
A.
timeOfTakeoff
chosen
Indicates the specific time at which a takeoff event occurs.
-
B.
timeAfterTakeoff
Indicates that a specified time point occurs after the moment of takeoff in a flight or launch sequence.
-
C.
takeoffBase
Indicates the location or base from which a takeoff (such as of an aircraft or flight) originates.
-
D.
takeoffMethod
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
-
E.
takeoffCharacteristic
Indicates the specific properties or conditions associated with how an entity takes off, such as its manner, performance, or requirements during takeoff.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.