Triple
T25616151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toxics Release Inventory |
E642165
|
entity |
| Predicate | dataAvailableFromYear |
P76522
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Toxics Release Inventory, dataAvailableFromYear, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAvailableFromYear Context triple: [Toxics Release Inventory, dataAvailableFromYear, 1987]
-
A.
dataAvailableFrom
chosen
Indicates that a specified source or provider offers access to certain data starting from a particular point or under certain conditions.
-
B.
dataReleaseYear
Indicates the year in which the data was officially released or made publicly available.
-
C.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
-
D.
nationalYears
Indicates the span of years during which an entity was active or affiliated at the national level (e.g., on a national team or in a national role).
-
E.
dataReleaseDate
Indicates the date on which a particular dataset or piece of data is officially made available or published.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e7c0108190b8d98fd639f13c12 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5 p.m.