Triple
T1963882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12 Years a Slave |
E42644
|
entity |
| Predicate | timeSettingEndYear |
P34444
|
FINISHED |
| Object | 1853 |
—
|
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: 1853 | Statement: [12 Years a Slave, timeSettingEndYear, 1853]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSettingEndYear Context triple: [12 Years a Slave, timeSettingEndYear, 1853]
-
A.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
B.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
-
C.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
D.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb6893eb881908923f0168374596a |
completed | March 7, 2026, 5:24 a.m. |
Created at: March 4, 2026, 7:36 p.m.