Triple
T13839949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tariff of 1816 |
E332630
|
entity |
| Predicate | supportedByRegion |
P5438
|
FINISHED |
| Object | Northeastern states |
—
|
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: Northeastern states | Statement: [Tariff of 1816, supportedByRegion, Northeastern states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByRegion Context triple: [Tariff of 1816, supportedByRegion, Northeastern states]
-
A.
supportsRegion
chosen
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
C.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
D.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ae5e4c8190ad85ad2968bc71b2 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.