Triple
T36554754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONZM |
E901671
|
entity |
| Predicate | lowerRankInSameOrder |
P12410
|
FINISHED |
| Object | Member of the New Zealand Order of Merit (MNZM) |
—
|
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: Member of the New Zealand Order of Merit (MNZM) | Statement: [ONZM, lowerRankInSameOrder, Member of the New Zealand Order of Merit (MNZM)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerRankInSameOrder Context triple: [ONZM, lowerRankInSameOrder, Member of the New Zealand Order of Merit (MNZM)]
-
A.
lowerRankedOrder
chosen
Indicates that one entity holds a lower rank or priority in an ordered sequence relative to another entity.
-
B.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
C.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
-
D.
lowerOrEqualRankTitle
Indicates that one entity’s rank or title is lower than or equal to the rank or title of another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.