Triple

T3157832
Position Surface form Disambiguated ID Type / Status
Subject Magic Gaming E66028 entity
Predicate basedIn P40 FINISHED
Object Orlando, Florida E11265 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: Orlando, Florida | Statement: [Magic Gaming, basedIn, Orlando, Florida]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orlando, Florida
Context triple: [Magic Gaming, basedIn, Orlando, Florida]
  • A. Orlando chosen
    Orlando is a major city in central Florida known for its theme parks, tourism industry, and entertainment attractions.
  • B. Orlando
    Orlando is a historic township area within Soweto, South Africa, known for its central role in the anti-apartheid struggle and vibrant local culture.
  • C. Orlando
    Orlando is a common Italian surname borne by numerous individuals, including notable political and cultural figures.
  • D. Kissimmee, Florida
    Kissimmee, Florida is a central Florida city in Osceola County known for its proximity to major Orlando-area theme parks and tourist attractions.
  • E. Jacksonville, Florida
    Jacksonville, Florida is a major city in northeastern Florida known for its extensive riverfront, large land area, and role as a regional economic and transportation hub.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad85850c1481908a9e9c6242238de2 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada5ec0da88190a83f3448ac76e98e completed March 8, 2026, 4:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b402b6f23081909aea1345a2938113 completed March 13, 2026, 12:27 p.m.
Created at: March 8, 2026, 3:05 p.m.