Triple
T1765790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General |
E38759
|
entity |
| Predicate | equivalentNavalRank |
P19071
|
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: [General, equivalentNavalRank, Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentNavalRank Context triple: [General, equivalentNavalRank, Admiral]
-
A.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
-
C.
rankEquivalent
chosen
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
D.
promotedToViceAdmiral
Indicates that an entity has been elevated in rank or position to the role of Vice Admiral.
-
E.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.