Triple
T25038361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Commodore |
E627041
|
entity |
| Predicate | navalEquivalent |
P56193
|
FINISHED |
| Object | Commodore |
—
|
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: Commodore | Statement: [Air Commodore, navalEquivalent, Commodore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalEquivalent Context triple: [Air Commodore, navalEquivalent, Commodore]
-
A.
nonNavalEquivalent
Indicates that one entity serves as the non-naval (e.g., land or air) counterpart or equivalent of another entity that is naval.
-
B.
navalAnalogue
chosen
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
C.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
D.
navalDiscipline
Indicates the enforcement or maintenance of rules, order, and conduct within a naval or maritime context.
-
E.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:08 a.m.