Triple
T4985575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Channel Fleet |
E111993
|
entity |
| Predicate | heldByRank |
P7007
|
FINISHED |
| Object | 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: Admiral | Statement: [Commander-in-Chief, Channel Fleet, heldByRank, Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByRank Context triple: [Commander-in-Chief, Channel Fleet, heldByRank, Admiral]
-
A.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.