Triple
T34988755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiaolin Showdown |
E1009324
|
entity |
| Predicate | competitionMechanic |
P72312
|
FINISHED |
| Object | Xiaolin Showdown duels |
—
|
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: Xiaolin Showdown duels | Statement: [Xiaolin Showdown, competitionMechanic, Xiaolin Showdown duels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionMechanic Context triple: [Xiaolin Showdown, competitionMechanic, Xiaolin Showdown duels]
-
A.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
B.
competitionSystem
chosen
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
-
C.
competitiveGame
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:01 p.m.