Triple
T8809976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral of the Red |
E209632
|
entity |
| Predicate | natureOfRank |
P84723
|
FINISHED |
| Object | senior flag rank |
—
|
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: senior flag rank | Statement: [Admiral of the Red, natureOfRank, senior flag rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfRank Context triple: [Admiral of the Red, natureOfRank, senior flag rank]
-
A.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
B.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
D.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
-
E.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd69df4819091e9a7dad87265a4 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.