Triple
T30963273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borden government |
E788884
|
entity |
| Predicate | laterFormedAs |
P109904
|
FINISHED |
| Object | Union government |
—
|
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: Union government | Statement: [Borden government, laterFormedAs, Union government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterFormedAs Context triple: [Borden government, laterFormedAs, Union government]
-
A.
laterBecameKnownAs
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
B.
divisionFormedFrom
Indicates that an organizational division was created by splitting off from or being reorganized out of another existing entity.
-
C.
laterRefoundedAs
chosen
Indicates that an entity was dissolved or ceased to exist and was subsequently re-established under a new or modified form, identity, or organization.
-
D.
laterParentFormation
Indicates that the parent entity is formed or established at a later time than the related entity.
-
E.
laterSyncretizedWith
Indicates that one element was subsequently merged or conflated with another into a single, combined form or identity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: April 29, 2026, 8:54 p.m.