Triple
T27614554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OOM |
E700404
|
entity |
| Predicate | higherGradeInOrder |
P63520
|
FINISHED |
| Object | Commander of the Order of Merit of the Police Forces |
—
|
NE NERFINISHED |
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: Commander of the Order of Merit of the Police Forces | Statement: [OOM, higherGradeInOrder, Commander of the Order of Merit of the Police Forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherGradeInOrder Context triple: [OOM, higherGradeInOrder, Commander of the Order of Merit of the Police Forces]
-
A.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
hasGradeWithinOrder
Indicates that one entity’s grade or rank falls within a specified ordered range or position relative to another entity.
-
C.
upperGrade
chosen
Indicates that one entity is in a higher grade level than another entity.
-
D.
lowerRankedOrder
Indicates that one entity holds a lower rank or priority in an ordered sequence relative to another entity.
-
E.
orderGradeLevel
Indicates the relative sequencing or ranking of grade levels, specifying which grade comes before or after another.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 2:12 p.m.