Triple
T10120146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuanku Imran |
E223264
|
entity |
| Predicate | honorificPrefix |
P536
|
FINISHED |
| Object | Tuanku |
E808712
|
NE 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: Tuanku | Statement: [Tuanku Imran, honorificPrefix, Tuanku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tuanku Context triple: [Tuanku Imran, honorificPrefix, Tuanku]
-
A.
Tuanku
chosen
Tuanku is a Malay royal honorific style traditionally used for reigning monarchs and high-ranking nobility in Malaysia.
-
B.
Tuan Besar
Tuan Besar was a Malay honorific title denoting the ruling White Rajah of Sarawak, signifying his status as the paramount leader.
-
C.
Tribhuwana
Tribhuwana is the regnal name of a 14th-century Javanese queen of the Majapahit Empire, formally known as Tribhuwana Wijayatunggadewi.
-
D.
Tunku
Tunku is a Malay royal honorific title traditionally used by members of certain royal families in Malaysia.
-
E.
Prabu
Prabu is a royal title historically used for kings or rulers in the Sundanese Kingdom of West Java, Indonesia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2659cdc8190b3ba91426bda55ec |
completed | April 2, 2026, 2:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e5b6101081909c97956591b01af9 |
completed | April 5, 2026, 10:44 p.m. |
Created at: March 30, 2026, 9:04 p.m.