Triple

T16721739
Position Surface form Disambiguated ID Type / Status
Subject Thomas J. Whitmore E406363 entity
Predicate officeAssumedInFiction P124378 FINISHED
Object mid-1990s 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: mid-1990s | Statement: [Thomas J. Whitmore, officeAssumedInFiction, mid-1990s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: officeAssumedInFiction
Context triple: [Thomas J. Whitmore, officeAssumedInFiction, mid-1990s]
  • A. usedInFictionalWork
    Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
  • B. hasFictionalWork
    Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
  • C. livesInFiction
    Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
  • D. attendedByFictionalCharacter
    Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
  • E. fictionalCharacterAssociatedWith
    Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
  • 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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38743750c81908a980372ad8f1a6a completed April 18, 2026, 1:29 p.m.
PD Predicate disambiguation batch_69e319c379f88190ac0adf812486f598 completed April 18, 2026, 5:42 a.m.
PDg Predicate description generation batch_69e326b9e84881909a9166e65bd850d6 completed April 18, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:20 a.m.