Triple
T9219701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaël Perdriau |
E221329
|
entity |
| Predicate | publicOfficeType |
P5164
|
FINISHED |
| Object | mayor |
—
|
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: mayor | Statement: [Gaël Perdriau, publicOfficeType, mayor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOfficeType Context triple: [Gaël Perdriau, publicOfficeType, mayor]
-
A.
hasOfficeType
chosen
Indicates that an entity’s office is classified as a specific type or category of office.
-
B.
governsOfficeType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of office.
-
C.
definesOfficeOf
Indicates that one entity specifies or establishes the official role, position, or office associated with another entity.
-
D.
typeOfOffice
Indicates the specific category or kind of office that an office entity belongs to (e.g., executive, legislative, judicial, or other office types).
-
E.
governingOffice
Indicates the official position or office through which an entity exercises governing authority over a jurisdiction or organization.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda74808081908d4bf890759e7120 |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.