Triple
T48945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tea Act |
E961
|
entity |
| Predicate | colonialPerception |
P3167
|
FINISHED |
| Object | viewed as a violation of colonial rights |
—
|
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: viewed as a violation of colonial rights | Statement: [Tea Act, colonialPerception, viewed as a violation of colonial rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialPerception Context triple: [Tea Act, colonialPerception, viewed as a violation of colonial rights]
-
A.
hadColonialAdministrationType
Indicates the specific form or system of colonial governance that was exercised over a territory or population.
-
B.
wasColonyOf
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
C.
nationalityRepresented
Indicates the country or nation that an entity officially represents, typically in a professional, competitive, or diplomatic capacity.
-
D.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
E.
languageOfOpinion
Indicates that a particular opinion is expressed or communicated in a specified language.
- F. None of above. chosen
Provenance (4 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c198e74819088a211001d0b54d4 |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.