Triple
T11544228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroic Tavern Brawl |
E273741
|
entity |
| Predicate | entryFee |
P3997
|
FINISHED |
| Object | gold or real-money equivalent |
—
|
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: gold or real-money equivalent | Statement: [Heroic Tavern Brawl, entryFee, gold or real-money equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryFee Context triple: [Heroic Tavern Brawl, entryFee, gold or real-money equivalent]
-
A.
admissionFee
chosen
Indicates the monetary charge required for entry or participation in a place, event, or activity.
-
B.
registrationFee
Indicates the monetary amount required to register for a service, event, or entity.
-
C.
franchiseFee
Indicates the monetary fee that a franchisee must pay to a franchisor in exchange for the right to operate under the franchisor’s brand or system.
-
D.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
E.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
- F. None of above.
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_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. |
Created at: April 8, 2026, 9:37 p.m.