Triple
T34059690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate building, Phnom Penh |
E873457
|
entity |
| Predicate | legislativeBodyNameServed |
P77343
|
FINISHED |
| Object | Senate of Cambodia |
—
|
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: Senate of Cambodia | Statement: [Senate building, Phnom Penh, legislativeBodyNameServed, Senate of Cambodia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeBodyNameServed Context triple: [Senate building, Phnom Penh, legislativeBodyNameServed, Senate of Cambodia]
-
A.
legislatureServed
chosen
Indicates that an individual has served as a member of a specific legislative body during some period of time.
-
B.
legislatureTypeServed
Indicates the type of legislative body in which an entity has served (e.g., national, state, or local legislature).
-
C.
stateLegislativeBodyServedIn
Indicates the specific state-level legislative body in which an individual has served as a member.
-
D.
legislativeChamberServed
Indicates that an individual has served as a member of a specified legislative chamber.
-
E.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:52 a.m.