Triple
T37789229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSRS |
E942035
|
entity |
| Predicate | coverageChangeYear |
P194221
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [CSRS, coverageChangeYear, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageChangeYear Context triple: [CSRS, coverageChangeYear, 1984]
-
A.
changedInYear
Indicates that an entity underwent a change or modification during a specified calendar year.
-
B.
changedConfigurationInYear
Indicates that an entity altered or updated its configuration during a specified calendar year.
-
C.
coversFromYear
Indicates that something (such as a record, dataset, or agreement) applies starting from a specified year onward.
-
D.
routeChangesEveryYear
Indicates that the route is modified or updated on an annual basis.
-
E.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 3, 2026, 4:19 p.m.