Triple
T17263297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Félix Éboué |
E419058
|
entity |
| Predicate | appointedGovernorOfGuadeloupe |
P52727
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Félix Éboué, appointedGovernorOfGuadeloupe, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedGovernorOfGuadeloupe Context triple: [Félix Éboué, appointedGovernorOfGuadeloupe, 1936]
-
A.
colonialGovernor
chosen
Indicates a relationship where one entity serves as the governor or chief administrative authority of a colony belonging to another political power.
-
B.
provinceGovernor
Indicates that one entity serves as the governor or chief administrative authority of a particular province in relation to the other entity.
-
C.
currentGovernor
Indicates that one entity is the person who presently holds the office of governor of the other entity.
-
D.
laterGovernor
Indicates that one entity subsequently became the governor of a place or jurisdiction associated with another entity.
-
E.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4379848190add32ba8e5f93527 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.