Triple
T28308663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Crown of Johor |
E713937
|
entity |
| Predicate | usesHonourificSystem |
P9810
|
FINISHED |
| Object | Johor 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: Johor honours system | Statement: [Order of the Crown of Johor, usesHonourificSystem, Johor honours system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHonourificSystem Context triple: [Order of the Crown of Johor, usesHonourificSystem, Johor honours system]
-
A.
hasHonorificSystem
chosen
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
-
B.
honorificUse
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
C.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
D.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address to 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:39 p.m.