Triple
T241264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventory of U.S. Greenhouse Gas Emissions and Sinks |
E4936
|
entity |
| Predicate | temporalCoverageStart |
P288
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Inventory of U.S. Greenhouse Gas Emissions and Sinks, temporalCoverageStart, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalCoverageStart Context triple: [Inventory of U.S. Greenhouse Gas Emissions and Sinks, temporalCoverageStart, 1990]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
C.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
D.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
E.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b60ad308190b12f119960a8bde7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.