Triple
T23927091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Colony of British Columbia |
E602386
|
entity |
| Predicate | reasonForUnion |
P2658
|
FINISHED |
| Object | administrative efficiency |
—
|
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: administrative efficiency | Statement: [United Colony of British Columbia, reasonForUnion, administrative efficiency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForUnion Context triple: [United Colony of British Columbia, reasonForUnion, administrative efficiency]
-
A.
reasonForMerger
chosen
Indicates the underlying cause, motivation, or justification for why two or more entities merged.
-
B.
endedUnionBetween
Indicates that one entity caused or marked the termination of a union, alliance, or partnership with another entity.
-
C.
reasonForAssociation
Indicates that one entity is associated with another due to a specific cause, purpose, or motivating factor underlying their relationship.
-
D.
reasonForAlliance
Indicates that one entity’s motivation, cause, or justification for forming an alliance is based on another specified factor or entity.
-
E.
confirmedUnionWith
Indicates that a previously proposed or potential union between entities has been formally verified and accepted as established.
- 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.