Triple
T19115371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice-Admiral of the Blue |
E467892
|
entity |
| Predicate | precedenceOrder |
P77735
|
FINISHED |
| Object | below Admiral of the Blue |
—
|
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: below Admiral of the Blue | Statement: [Vice-Admiral of the Blue, precedenceOrder, below Admiral of the Blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedenceOrder Context triple: [Vice-Admiral of the Blue, precedenceOrder, below Admiral of the Blue]
-
A.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
B.
orderOfPrecedenceGroup
Indicates the hierarchical ranking or priority grouping of entities relative to one another.
-
C.
orderOfPrecedenceHigher
chosen
Indicates that one entity holds a higher rank or priority than another in an established order of precedence.
-
D.
bindingPrecedent
Indicates that a prior decision or ruling must be followed as an authoritative legal standard in deciding a current case.
-
E.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39736588190b80ddef77101641a |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.