Triple
T194274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Townshend Acts (tea tax component) |
E3784
|
entity |
| Predicate | imposedOn |
P7076
|
FINISHED |
| Object | imported tea |
—
|
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: imported tea | Statement: [Townshend Acts (tea tax component), imposedOn, imported tea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imposedOn Context triple: [Townshend Acts (tea tax component), imposedOn, imported tea]
-
A.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
B.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
C.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
D.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
E.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a256769ad8819083c1d83082c0215e |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.