Triple
T24516284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FUNCINPEC |
E606377
|
entity |
| Predicate | officeHolderFromParty |
P9178
|
FINISHED |
| Object | Norodom Ranariddh |
—
|
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: Norodom Ranariddh | Statement: [FUNCINPEC, officeHolderFromParty, Norodom Ranariddh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderFromParty Context triple: [FUNCINPEC, officeHolderFromParty, Norodom Ranariddh]
-
A.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
B.
determinedOfficeHolderOf
Indicates that an authority or process has officially selected or designated a specific individual to hold a particular office or position.
-
C.
officeHolderIs
Indicates that one entity serves as the office holder (e.g., official or position occupant) of another entity, such as an office, role, or institution.
-
D.
officeHolderTypicallyFrom
Indicates that the person holding a particular office is typically drawn from or originates from a specified group, region, or category.
-
E.
politicalPartyLeader
chosen
Indicates that one entity serves as the leader or head of a specified political party.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.