Triple

T31706047
Position Surface form Disambiguated ID Type / Status
Subject The Adventure of the Reigate Squire E809182 entity
Predicate fictionalTimeSetting P180185 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: [The Adventure of the Reigate Squire, fictionalTimeSetting, Victorian era]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalTimeSetting
Context triple: [The Adventure of the Reigate Squire, fictionalTimeSetting, Victorian era]
  • A. fictionalTime
    Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
  • B. periodOfFictionalSetting chosen
    Indicates the time period in which the events of a fictional work are set.
  • C. workOfFictionSetting
    Indicates that a work of fiction is set in, or primarily takes place within, a particular location, time, or environment.
  • D. fictionalEra
    Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
  • E. fictionalTimeDepth
    Indicates a relationship where an entity is associated with a time period or temporal depth that exists only within a fictional or imagined context.
  • 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_69f348de914081909fc8edff56f34dbe completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: April 30, 2026, 11:13 p.m.