Triple
T9478627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Review Tribunal of New Zealand |
E228576
|
entity |
| Predicate | hearsClaimsOn |
P88348
|
FINISHED |
| Object | human rights |
—
|
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: human rights | Statement: [Human Rights Review Tribunal of New Zealand, hearsClaimsOn, human rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsClaimsOn Context triple: [Human Rights Review Tribunal of New Zealand, hearsClaimsOn, human rights]
-
A.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
hearsFrom
Indicates that one entity receives information, communication, or a message from another entity.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
E.
hearsCasesAgainst
Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8014fd0c819093bd15816f3db357 |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:54 p.m.