Triple
T36405782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of Malaysia |
E896744
|
entity |
| Predicate | usesHonorificForJudges |
P119748
|
FINISHED |
| Object | Justice |
—
|
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: Justice | Statement: [Court of Appeal of Malaysia, usesHonorificForJudges, Justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHonorificForJudges Context triple: [Court of Appeal of Malaysia, usesHonorificForJudges, Justice]
-
A.
honorificUse
chosen
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
hasHonorificSystem
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
-
C.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
D.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
-
E.
usesLayJudges
Indicates that a legal system, court, or trial incorporates lay judges—non-professional, typically citizen adjudicators—into its decision-making process.
- 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_69f76e53b81081908d3b81860593f38a |
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_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.