Triple
T11186339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Françoise-Améthyste Christophe |
E264676
|
entity |
| Predicate | hasFatherRole |
P38221
|
FINISHED |
| Object | Haitian revolutionary leader |
—
|
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: Haitian revolutionary leader | Statement: [Françoise-Améthyste Christophe, hasFatherRole, Haitian revolutionary leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFatherRole Context triple: [Françoise-Améthyste Christophe, hasFatherRole, Haitian revolutionary leader]
-
A.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
B.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
hasMemberFather
Indicates that an entity is a member of a group or organization by virtue of their father’s membership or paternal relationship.
-
D.
hasFatherPosition
Indicates that the position, role, or job held by an entity’s father is being specified or linked to that entity.
-
E.
hasHostFather
Indicates a relationship where one person serves as the host father of another, typically in a hosting or exchange 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8abbeac8190ad6e419258999f4e |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.