Triple
T37529767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | town of Redemption |
E932999
|
entity |
| Predicate | hasTournamentRule |
P118112
|
FINISHED |
| Object | duels decided by fastest draw |
—
|
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: duels decided by fastest draw | Statement: [town of Redemption, hasTournamentRule, duels decided by fastest draw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentRule Context triple: [town of Redemption, hasTournamentRule, duels decided by fastest draw]
-
A.
hasTournamentType
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
-
B.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
C.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
-
D.
hasTournamentLevel
Indicates that an entity participates in or is classified by a specific competitive or organizational level within a tournament structure.
-
E.
hasVenueRules
chosen
Indicates that specific rules or policies are associated with, or apply to, a particular venue.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:17 p.m.