Triple
T32623315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers W 33 Bremen |
E833987
|
entity |
| Predicate | notableFlightDirection |
P193894
|
FINISHED |
| Object | east‑to‑west |
—
|
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: east‑to‑west | Statement: [Junkers W 33 Bremen, notableFlightDirection, east‑to‑west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFlightDirection Context triple: [Junkers W 33 Bremen, notableFlightDirection, east‑to‑west]
-
A.
directionOfHistoricFlight
chosen
Indicates the compass direction or route orientation taken by a historically significant flight.
-
B.
natureOfFlight
Indicates the general type or characteristics of a flight, such as its purpose, category, or operational nature.
-
C.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
-
D.
travelsDirection
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
E.
positionFlown
Indicates the specific role or seat (e.g., pilot, co-pilot) that an individual occupied while operating or flying in an aircraft.
- 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:06 a.m.