Triple
T5286324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand |
E119627
|
entity |
| Predicate | hasHonoursSystem |
P12022
|
FINISHED |
| Object | New Zealand royal honours system |
—
|
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: New Zealand royal honours system | Statement: [New Zealand, hasHonoursSystem, New Zealand royal honours system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonoursSystem Context triple: [New Zealand, hasHonoursSystem, New Zealand royal honours system]
-
A.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
B.
hasHonorsCollege
Indicates that an educational institution includes or is associated with an honors college program.
-
C.
belongsToHonoursSystem
chosen
Indicates that something is a component or member of a specific honours or awards system.
-
D.
isHonorSocietyFor
Indicates that an organization functions as an honor society specifically recognizing and serving the members of a particular group or field.
-
E.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.