Triple
T7443975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Medal (United Kingdom) |
E171823
|
entity |
| Predicate | rankScope |
P59486
|
FINISHED |
| Object | below commissioned officer |
—
|
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 commissioned officer | Statement: [Military Medal (United Kingdom), rankScope, below commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankScope Context triple: [Military Medal (United Kingdom), rankScope, below commissioned officer]
-
A.
rankingScope
chosen
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
C.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankFlagFor
Indicates that something is assigned or associated with a specific ranking flag used to mark its status or priority.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f36e9a588190b54b8bae181fc971 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:13 p.m.