Triple
T14569296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 59 |
E341866
|
entity |
| Predicate | airshipClass |
P114709
|
FINISHED |
| Object | LZ 38 class |
—
|
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: LZ 38 class | Statement: [LZ 59, airshipClass, LZ 38 class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airshipClass Context triple: [LZ 59, airshipClass, LZ 38 class]
-
A.
airshipBoss
Indicates that one entity serves as the primary controlling or commanding figure over an airship-related context or scenario involving another entity.
-
B.
airshipRegistration
Indicates the formal registration relationship between an airship and the authority or registry that records its official details and identification.
-
C.
aircraftPowered
Indicates that one entity (an aircraft) is powered or driven by another entity (such as an engine, motor, or propulsion system).
-
D.
airWingType
Indicates the classification or category of an air wing associated with an entity.
-
E.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.