Triple
T27414423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | province of Quebec |
E692851
|
entity |
| Predicate | confederationEntry |
P15931
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [province of Quebec, confederationEntry, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederationEntry Context triple: [province of Quebec, confederationEntry, 1867]
-
A.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
B.
enteredConfederation
chosen
Indicates that an entity became a member of, or formally joined, a confederation.
-
C.
confederation
Indicates a formal union or alliance between multiple entities that retain their individual autonomy while cooperating under a shared framework or agreement.
-
D.
confederation2
Indicates a formal alliance or union in which multiple entities join together under a shared framework while retaining their individual autonomy.
-
E.
associatedConfederation
Indicates a relationship where an entity is linked to, belongs to, or is formally connected with a specific confederation.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 12:33 p.m.