Triple
T32732616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional Monarchy of Pahang |
E836993
|
entity |
| Predicate | hasCabinetLikeBody |
P10249
|
FINISHED |
| Object | Pahang State Executive Council |
—
|
NE NERFINISHED |
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: Pahang State Executive Council | Statement: [Constitutional Monarchy of Pahang, hasCabinetLikeBody, Pahang State Executive Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabinetLikeBody Context triple: [Constitutional Monarchy of Pahang, hasCabinetLikeBody, Pahang State Executive Council]
-
A.
hasCabinet
chosen
Indicates that one entity possesses, includes, or is equipped with a cabinet associated with it.
-
B.
isInCabinet
Indicates that one entity serves as a member of the governing cabinet associated with another entity (such as a government or administration).
-
C.
hasBodyCavity
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
D.
cabinetType
Indicates the specific kind or category of cabinet associated with an entity.
-
E.
hasCabinetName
Indicates that an entity is associated with a specific cabinet by its name.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 1, 2026, 1:11 a.m.