Triple
T36825892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italia expedition |
E910007
|
entity |
| Predicate | airshipDesigner |
P186326
|
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: [Italia expedition, airshipDesigner, Umberto Nobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airshipDesigner Context triple: [Italia expedition, airshipDesigner, Umberto Nobile]
-
A.
airshipClass
Indicates the classification or type category to which an airship belongs.
-
B.
airshipHeritage
Indicates a relationship where one entity preserves, represents, or is historically derived from the tradition, technology, or legacy of airships.
-
C.
airframeDesigner
Indicates that one entity is the designer or design authority responsible for the airframe of an aircraft or aerospace vehicle associated with the other entity.
-
D.
appliedToAircraftDesignedBy
Indicates that something (such as a component, system, or regulation) is applied to an aircraft that was designed by a specified designer or organization.
-
E.
airshipNumber
Indicates the identifying number assigned to a specific airship within a set or system.
- F. None of above. chosen
Provenance (4 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_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:13 p.m.