Triple
T32933886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMN |
E842473
|
entity |
| Predicate | styleOfAddressAssociated |
P64298
|
FINISHED |
| Object | Yang Amat Berbahagia |
—
|
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: Yang Amat Berbahagia | Statement: [SMN, styleOfAddressAssociated, Yang Amat Berbahagia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfAddressAssociated Context triple: [SMN, styleOfAddressAssociated, Yang Amat Berbahagia]
-
A.
isStyleOfAddress
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
B.
usedInStyleOfAddress
chosen
Indicates that one entity is used as a form or style of address when referring to or speaking to another entity.
-
C.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
D.
addressingMethod
Indicates the manner or form of address one entity uses when speaking or referring to another entity.
-
E.
addressedWith
Indicates that one entity is referred to or spoken to using a particular name, title, or form of address.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:20 a.m.