Triple
T23927094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Colony of British Columbia |
E602386
|
entity |
| Predicate | joinedConfederationWith |
P15931
|
FINISHED |
| Object | Canada |
—
|
NE NERFINISHED |
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: Canada | Statement: [United Colony of British Columbia, joinedConfederationWith, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedConfederationWith Context triple: [United Colony of British Columbia, joinedConfederationWith, Canada]
-
A.
enteredConfederation
chosen
Indicates that an entity became a member of, or formally joined, a confederation.
-
B.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
C.
associatedConfederation
Indicates a relationship where an entity is linked to, belongs to, or is formally connected with a specific confederation.
-
D.
confederationFoundedBy
Indicates that a confederation was established or created by a specific person, group, or entity.
-
E.
formedConfederation
Indicates that two or more entities joined together to create a confederation, establishing a formal union or alliance among them.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1e13e8819096432b8133c7d71e |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:48 p.m.