Triple

T37544539
Position Surface form Disambiguated ID Type / Status
Subject Memphis Grizzlies (WFL proposed rename) E933421 entity
Predicate hasProposedHomeState P79153 FINISHED
Object Tennessee E17093 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: Tennessee | Statement: [Memphis Grizzlies (WFL proposed rename), hasProposedHomeState, Tennessee]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProposedHomeState
Context triple: [Memphis Grizzlies (WFL proposed rename), hasProposedHomeState, Tennessee]
  • A. hasProposed
    Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
  • B. hasProposedOutcome
    Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
  • C. hasProposedRole
    Indicates that one entity has suggested or put forward a specific role or position for another entity.
  • D. hasHomeProvinceOrState chosen
    Indicates that an entity is associated with a particular province or state as its home or primary regional location.
  • E. hasHome
    Indicates that an entity possesses or is associated with a place where it lives or is based.
  • 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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c8efcd4819088c2aeead65d93df completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40a7ec19c0819085d68adc48bf3ed9 completed June 28, 2026, 4:49 a.m.
PD Predicate disambiguation batch_6a037a1553e08190bb7424c448cb1f33 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:17 p.m.