Triple
T31260670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pohnpei State Government |
E797107
|
entity |
| Predicate | hasDeputyExecutiveHeadTitle |
P3014
|
FINISHED |
| Object | Lieutenant Governor |
—
|
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: Lieutenant Governor | Statement: [Pohnpei State Government, hasDeputyExecutiveHeadTitle, Lieutenant Governor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeputyExecutiveHeadTitle Context triple: [Pohnpei State Government, hasDeputyExecutiveHeadTitle, Lieutenant Governor]
-
A.
deputyExecutiveHeadTitle
chosen
Indicates the official job title held by a person serving as the deputy to an organization's executive head.
-
B.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
C.
hasExecutiveHeadTitle
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
D.
hasDeputyHeads
Indicates that an entity has one or more individuals serving in subordinate leadership roles as deputy heads.
-
E.
hasMinisterTitle
Indicates that an entity holds or is associated with a specific ministerial title or office.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 9:12 p.m.