Triple
T36826015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 |
E910011
|
entity |
| Predicate | hasCrewOnHistoricFlight |
P24228
|
FINISHED |
| Object | Umberto Nobile |
—
|
NE NERFINISHED |
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: Umberto Nobile | Statement: [N-1, hasCrewOnHistoricFlight, Umberto Nobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewOnHistoricFlight Context triple: [N-1, hasCrewOnHistoricFlight, Umberto Nobile]
-
A.
hasFlightCrew
Indicates that an entity (such as a flight or aircraft) is associated with one or more people serving as its flight crew.
-
B.
firstCrewedTestFlightCrew
chosen
Indicates that the subject is a member of the crew on the first crewed test flight of the referenced vehicle or mission.
-
C.
officiallyFlownOn
Indicates that something has been formally carried or transported aboard a specific flight or aircraft under official or authorized status.
-
D.
dateOfNotableFlight
Indicates the calendar date on which a particular notable or significant flight took place.
-
E.
isPilotOf
Indicates that one entity serves as the pilot who operates or controls another entity, typically a vehicle or 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:13 p.m.