Triple

T22708723
Position Surface form Disambiguated ID Type / Status
Subject Anchor Drops E561532 entity
Predicate hasTrack P3284 FINISHED
Object Resolution 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: Resolution | Statement: [Anchor Drops, hasTrack, Resolution]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Resolution
Context triple: [Anchor Drops, hasTrack, Resolution]
  • A. Resolution chosen
    "Resolution" is a jazz fusion composition by the Mahavishnu Orchestra, featured on their influential 1973 album *Birds of Fire*.
  • B. Resolve
    "Resolve" is a song featured on the Foo Fighters' 2005 double album *In Your Honor*.
  • C. "Resolution"
    "Resolution" is a 2019 Doctor Who New Year’s Day special episode featuring the Thirteenth Doctor and her companions facing a revived Dalek threat.
  • D. Final Resolution
    Final Resolution is a professional wrestling pay-per-view event series produced by Impact Wrestling (formerly TNA), typically featuring major storyline culminations and championship matches.
  • E. RES
    RES is the IATA airport code for Resistencia International Airport serving the city of Resistencia in Argentina.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2454f1348819088d83f420925a5c1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f178d11d4081909981872698b6c45e completed April 29, 2026, 3:19 a.m.
Created at: April 17, 2026, 3:17 p.m.