Triple
T25038360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Commodore |
E627041
|
entity |
| Predicate | nonNavalEquivalent |
P157568
|
FINISHED |
| Object | Brigadier |
—
|
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: Brigadier | Statement: [Air Commodore, nonNavalEquivalent, Brigadier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonNavalEquivalent Context triple: [Air Commodore, nonNavalEquivalent, Brigadier]
-
A.
nonCombatEquivalentOf
Indicates that one entity serves as the non-combat or peaceful counterpart of another entity that is oriented toward combat or warfare.
-
B.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
C.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
D.
navalAuxiliary
Indicates that one entity serves as a supporting or auxiliary naval vessel or service for another entity.
-
E.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f45308d3148190bc24a7cdb570e866 |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:08 a.m.