Triple
T1205538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Medal |
E25878
|
entity |
| Predicate | rankRestriction |
P25564
|
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, rankRestriction, below commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRestriction Context triple: [Military Medal, rankRestriction, below commissioned officer]
-
A.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
B.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
C.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
D.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
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. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc0f8d08190b340012a9eb26275 |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bcc82e38819081c3615e1cc7a66f |
completed | March 1, 2026, 10:25 p.m. |
Created at: March 1, 2026, 7:46 p.m.