Triple
T33028943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Renaming |
E845112
|
entity |
| Predicate | occurredAroundYear |
P13193
|
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: [Great Renaming, occurredAroundYear, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredAroundYear Context triple: [Great Renaming, occurredAroundYear, 1987]
-
A.
approximateBirthYear
Indicates that the associated year is an estimated or inferred value for when an entity was born, rather than an exact known birth year.
-
B.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
C.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
D.
livedApproximately
Indicates that an entity’s lifespan or period of residence is known only roughly, with approximate rather than exact dates.
-
E.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:24 a.m.