Triple

T24440917
Position Surface form Disambiguated ID Type / Status
Subject Minnie McCoy E616258 entity
Predicate performingNameOrigin P72841 FINISHED
Object Memphis, Tennessee E2650 NE 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: Memphis, Tennessee | Statement: [Minnie McCoy, performingNameOrigin, Memphis, Tennessee]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: performingNameOrigin
Context triple: [Minnie McCoy, performingNameOrigin, Memphis, Tennessee]
  • A. performingNameDerivedFrom chosen
    Indicates that the name used for a performance or performing entity is derived from another name (such as a legal, original, or canonical name).
  • B. characterNameOrigin
    Indicates the source or inspiration from which a character’s name is derived.
  • C. performerOrigin
    Indicates that a performer originates from, or is associated with, a particular place or region.
  • D. hasNameOrigin
    Indicates that the origin or source of an entity’s name is specified by the related entity.
  • E. hasPerformerGivenName
    Indicates that a performer is associated with a specific given (first) name.
  • F. None of above.

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_69e2d7ec44b081909ccaf1f3bbec0641 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2978bb5a0819087ef151937923b0a completed April 29, 2026, 11:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a101bd549648190a2bbc355cf2b1251 completed May 22, 2026, 9:03 a.m.
PD Predicate disambiguation batch_69f287d3237c819099559c00f83131d8 completed April 29, 2026, 10:36 p.m.
Created at: April 18, 2026, 2:17 a.m.