Triple
T11809496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superfund excise taxes |
E280832
|
entity |
| Predicate | suspendedInYear |
P42789
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Superfund excise taxes, suspendedInYear, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspendedInYear Context triple: [Superfund excise taxes, suspendedInYear, 1995]
-
A.
suspensionYear
chosen
Indicates the year in which a suspension (such as a ban, halt, or temporary discontinuation of activity) takes effect or is recorded.
-
B.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
C.
suspendedFrom
Indicates that one entity is hanging or held up in the air by being attached to another supporting entity.
-
D.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
E.
suspendedForSeason
Indicates that an entity (typically a player or participant) is prohibited from taking part in all activities or competitions for the duration of an entire season.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.