Triple
T6362595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Turner |
E143145
|
entity |
| Predicate | portraysHistoricalPeriod |
P36351
|
FINISHED |
| Object | Victorian era |
—
|
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: Victorian era | Statement: [Mr. Turner, portraysHistoricalPeriod, Victorian era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysHistoricalPeriod Context triple: [Mr. Turner, portraysHistoricalPeriod, Victorian era]
-
A.
portraysHumanHistoryAs
Indicates that one entity represents or depicts human history in a particular way or from a specific perspective.
-
B.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
D.
appearsInTimePeriodDepicted
Indicates that something is present or occurs within the specific time period that is depicted or represented.
-
E.
historicalFocus
chosen
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680c02b481908618317566e31a5c |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.