Triple
T22945022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle of Zenda |
E569840
|
entity |
| Predicate | temporalSettingOfDepiction |
P68358
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Castle of Zenda, temporalSettingOfDepiction, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalSettingOfDepiction Context triple: [Castle of Zenda, temporalSettingOfDepiction, late 19th century]
-
A.
appearsInTimePeriodDepicted
chosen
Indicates that something is present or occurs within the specific time period that is depicted or represented.
-
B.
depictionOfTime
Indicates that one entity visually represents or symbolizes a specific moment, period, or progression of time associated with another entity.
-
C.
startTimeDepicted
Indicates that the subject visually represents the starting time of an event, process, or state.
-
D.
historicalSettingOfFilm
Indicates that a particular historical period, event, or context serves as the setting in which a film’s story takes place.
-
E.
filmLocationTime
Indicates that a film was shot at a particular location during a specific time or time period.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819c696c8190977bd2bca01509bc |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.