Triple
T17942978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral of the Fleet |
E448630
|
entity |
| Predicate | comparableRank |
P18223
|
FINISHED |
| Object | army general of the army |
—
|
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: army general of the army | Statement: [Admiral of the Fleet, comparableRank, army general of the army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparableRank Context triple: [Admiral of the Fleet, comparableRank, army general of the army]
-
A.
hasComparableRank
chosen
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
-
B.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
C.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
D.
isRankedAlongside
Indicates that two or more entities share the same or very similar rank, status, or position within a given ordering or hierarchy.
-
E.
canonicalRank
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad97611c8190a861467ae51f6c48 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.