Triple
T29053768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspector (New Zealand Police) |
E735333
|
entity |
| Predicate | badgeAuthority |
P90761
|
FINISHED |
| Object | warranted police 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: warranted police officer | Statement: [Inspector (New Zealand Police), badgeAuthority, warranted police officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeAuthority Context triple: [Inspector (New Zealand Police), badgeAuthority, warranted police officer]
-
A.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
B.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
-
C.
badgeCategory
Indicates the classification or type group to which a particular badge belongs.
-
D.
awardAuthority
chosen
Indicates that one entity grants another entity the power or right to give or confer awards.
-
E.
badgeVariesBy
Indicates that the characteristics or appearance of a badge change depending on some varying condition, context, or parameter.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66067f58c819087237fa88ad513cb |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:10 a.m.