Triple
T17668873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aline Chrétien |
E440459
|
entity |
| Predicate | spouseTermCoincidesWith |
P128484
|
FINISHED |
| Object | Jean Chrétien’s term as Prime Minister of Canada |
—
|
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: Jean Chrétien’s term as Prime Minister of Canada | Statement: [Aline Chrétien, spouseTermCoincidesWith, Jean Chrétien’s term as Prime Minister of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseTermCoincidesWith Context triple: [Aline Chrétien, spouseTermCoincidesWith, Jean Chrétien’s term as Prime Minister of Canada]
-
A.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
B.
coSpouse
Indicates that two individuals are married to each other as spouses.
-
C.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
D.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
E.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
- F. None of above. chosen
Provenance (4 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6723d081908eaa57eef6d70bd0 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:58 a.m.