Triple
T2195114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Colossus of Clout |
E49953
|
entity |
| Predicate | appliesToEra |
P36703
|
FINISHED |
| Object | 1920s |
—
|
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: 1920s | Statement: [The Colossus of Clout, appliesToEra, 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToEra Context triple: [The Colossus of Clout, appliesToEra, 1920s]
-
A.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
B.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
-
C.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
D.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf764e348190896af2aeb5520038 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbea8bd4881908f72019a5acf6174 |
completed | March 7, 2026, 5:59 a.m. |
Created at: March 4, 2026, 7:46 p.m.