Triple
T31267971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1725 |
E797301
|
entity |
| Predicate | effectOnColonialPolicy |
P65663
|
FINISHED |
| Object | facilitated British fort building in Maine |
—
|
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: facilitated British fort building in Maine | Statement: [Treaty of 1725, effectOnColonialPolicy, facilitated British fort building in Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnColonialPolicy Context triple: [Treaty of 1725, effectOnColonialPolicy, facilitated British fort building in Maine]
-
A.
impactOnColonies
chosen
Indicates the effect or influence that one factor, event, or condition has on colonies.
-
B.
colonialPolicyFeature
Indicates a characteristic, practice, or component that forms part of a colonial policy or system of colonial governance.
-
C.
colonialOutcome
Indicates the result or consequence of a colonial relationship or process between entities.
-
D.
colonialChange
Indicates a change in colonial status or control of a territory, such as gaining, losing, or altering colonial rule.
-
E.
effectOnPolity
Indicates the impact or consequence that one entity, event, or action has on a political body or governing organization.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 9:13 p.m.