Triple
T29627077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, West Indies Station |
E755172
|
entity |
| Predicate | hasTypicalRank |
P9317
|
FINISHED |
| Object | rear admiral |
—
|
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: rear admiral | Statement: [Commander-in-Chief, West Indies Station, hasTypicalRank, rear admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalRank Context triple: [Commander-in-Chief, West Indies Station, hasTypicalRank, rear admiral]
-
A.
typicalRank
chosen
Indicates the usual or most common rank or position an entity holds within a given ordering or hierarchy.
-
B.
typicalRankPrefix
Indicates that one entity is a commonly used or standard prefix attached to the rank represented by the other entity.
-
C.
typicalRankRange
Indicates the usual or most common range of ranks or ordered positions that an entity typically occupies within a ranking or hierarchy.
-
D.
hasRankOverℂ
Indicates that one entity has a specified (typically finite) linear-algebraic rank when considered over the field of complex numbers ℂ.
-
E.
hasRankNumber
Indicates that an entity is assigned a specific ordinal or hierarchical position represented by a numerical rank.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 6:38 p.m.