Triple

T11544225
Position Surface form Disambiguated ID Type / Status
Subject Tavern Brawl E273741 entity
Predicate distinctionFromArena P99983 FINISHED
Object does not require an entry fee in standard brawls 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: does not require an entry fee in standard brawls | Statement: [Tavern Brawl, distinctionFromArena, does not require an entry fee in standard brawls]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distinctionFromArena
Context triple: [Tavern Brawl, distinctionFromArena, does not require an entry fee in standard brawls]
  • A. arenaType
    Indicates the specific kind or category of arena associated with an entity or event.
  • B. homeArenaUntil
    Indicates that a particular venue served as an entity’s home arena up to a specified time or date.
  • C. distinctionFromPeers
    Indicates a relationship where an entity stands out or is differentiated from its peers based on notable characteristics, performance, or attributes.
  • D. formerArena
    Indicates that an entity was previously used as an arena but no longer serves that function.
  • E. associatedWithArena
    Indicates a relationship in which an entity is linked or connected to a particular arena, such as by location, use, affiliation, or operation.
  • 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_69d6aae4dfa48190a3ab0b19a159a3c5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d886e1d754819089f3b6be3404fa0b completed April 10, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69d8087cbe7c819085680f3d67ccc978 completed April 9, 2026, 8:13 p.m.
PDg Predicate description generation batch_69d822ef46988190a1c360da4ee14fef completed April 9, 2026, 10:06 p.m.
Created at: April 8, 2026, 9:37 p.m.