Triple

T30472192
Position Surface form Disambiguated ID Type / Status
Subject The Fabled City (early version) E775334 entity
Predicate hasWorkTitleDerivedFrom P88313 FINISHED
Object The Fabled City NE NERFINISHED

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: The Fabled City | Statement: [The Fabled City (early version), hasWorkTitleDerivedFrom, The Fabled City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleDerivedFrom
Context triple: [The Fabled City (early version), hasWorkTitleDerivedFrom, The Fabled City]
  • A. workFromWhichTitleDerived chosen
    Indicates that a title is derived from, or based on, a particular underlying work.
  • B. hasWorkTitleVariant
    Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
  • C. hasWorkTitleType
    Indicates that an entity holds a specific category or type of work-related title (e.g., job title type or role classification).
  • D. hasTitleWork
    Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
  • E. hasWorkingTitle
    Indicates that an entity is associated with a provisional or temporary title used during its development or production.
  • 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_69f22497341481909c21ba329fadaa6b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
Created at: April 29, 2026, 8:11 p.m.