Triple

T24203393
Position Surface form Disambiguated ID Type / Status
Subject Anaconda Vise E600037 entity
Predicate legalIn P155172 FINISHED
Object professional wrestling matches 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: professional wrestling matches | Statement: [Anaconda Vise, legalIn, professional wrestling matches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalIn
Context triple: [Anaconda Vise, legalIn, professional wrestling matches]
  • A. legality
    Indicates that an action, object, or situation conforms to, violates, or is evaluated in terms of formal laws or legal rules.
  • B. legalAct
    Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
  • C. legalLicenseIn
    Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
  • D. legalAuthorityIn
    Indicates that an entity holds official legal power, jurisdiction, or governing authority within a specified area or domain.
  • E. legalExceptionUnitedStates
    Indicates that the usual legal rule or requirement does not apply in the United States due to a specific statutory, regulatory, or judicially recognized exception.
  • 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_69e288ceaab88190899d0acb5931591d completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27ca38c148190ae65cd692567d43d completed April 29, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f1c43e55688190b55fc20274ed471c completed April 29, 2026, 8:41 a.m.
PDg Predicate description generation batch_69f1c9834064819082024233d9c6f98f completed April 29, 2026, 9:04 a.m.
Created at: April 17, 2026, 11:37 p.m.