Triple
T8028981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destruction of Zeppelin LZ 37 |
E186928
|
entity |
| Predicate | pilotRank |
P80664
|
FINISHED |
| Object | Flight Sub-Lieutenant |
—
|
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: Flight Sub-Lieutenant | Statement: [Destruction of Zeppelin LZ 37, pilotRank, Flight Sub-Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilotRank Context triple: [Destruction of Zeppelin LZ 37, pilotRank, Flight Sub-Lieutenant]
-
A.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
B.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
C.
airCommanderRank
Indicates that one entity holds the rank or position of air commander relative to another entity (such as a force, unit, or operation).
-
D.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
E.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ecdbc5881909246982b93978841 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.