Triple
T353118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut Colony |
E7484
|
entity |
| Predicate | statusDuringRevolution |
P4701
|
FINISHED |
| Object | rebel colony against British rule |
—
|
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: rebel colony against British rule | Statement: [Connecticut Colony, statusDuringRevolution, rebel colony against British rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringRevolution Context triple: [Connecticut Colony, statusDuringRevolution, rebel colony against British rule]
-
A.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
revolutionVictoryYear
Indicates the year in which a revolution achieved victory or successfully overthrew the existing regime.
-
D.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
-
E.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb80f524819093f4c2c18c3d615f |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.