Triple
T15770766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Gorontalo |
E382351
|
entity |
| Predicate | officeHoldsRole |
P13957
|
FINISHED |
| Object | chief executive of Gorontalo Province |
—
|
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: chief executive of Gorontalo Province | Statement: [Governor of Gorontalo, officeHoldsRole, chief executive of Gorontalo Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHoldsRole Context triple: [Governor of Gorontalo, officeHoldsRole, chief executive of Gorontalo Province]
-
A.
officeHolderRoleIn
Indicates that an entity holds or has held a specific role or position within a particular office or organizational context.
-
B.
officeItAbbreviatesRole
Indicates that an office title or designation serves as an abbreviation for a particular role or position.
-
C.
officeHolderRoleFor
Indicates that a specific role or position is held by an office holder within an organization or governing body.
-
D.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
-
E.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051962fe08190a6201dd48196a9ee |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.