Triple
T32934183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negeri Sembilan royal institutions |
E842482
|
entity |
| Predicate | hasCeremonialLanguage |
P2769
|
FINISHED |
| Object | Malay |
—
|
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: Malay | Statement: [Negeri Sembilan royal institutions, hasCeremonialLanguage, Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeremonialLanguage Context triple: [Negeri Sembilan royal institutions, hasCeremonialLanguage, Malay]
-
A.
languageOfCeremony
chosen
Indicates the language in which a ceremony is conducted or officially performed.
-
B.
ceremonialLanguageElement
Indicates a linguistic element that is specifically used within or associated with formal ceremonies or ritual contexts.
-
C.
hasCeremonialFunctions
Indicates that an entity performs or is associated with formal, ritualistic, or ceremonial roles or activities.
-
D.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
E.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
- 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:20 a.m.