Triple
T1768849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral of the Fleet of the Royal Navy |
E38826
|
entity |
| Predicate | NATOrankCode |
P24247
|
FINISHED |
| Object | OF-10 |
—
|
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: OF-10 | Statement: [Admiral of the Fleet of the Royal Navy, NATOrankCode, OF-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOrankCode Context triple: [Admiral of the Fleet of the Royal Navy, NATOrankCode, OF-10]
-
A.
NATORankCode
chosen
Indicates the standardized NATO rank classification assigned to a military person or position within the alliance.
-
B.
nationalRank
Indicates the position or standing of an entity within a ranking system at the national level.
-
C.
NATODesignation
Indicates that one entity is the official name or code assigned to another entity by NATO for identification or classification purposes.
-
D.
portRank
Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
-
E.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
- 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_69a8862e61708190af97b9838cc3f5de |
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.