Triple
T6547469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liguilla |
E151045
|
entity |
| Predicate | competitionSystem |
P72312
|
FINISHED |
| Object | playoff bracket |
—
|
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: playoff bracket | Statement: [Liguilla, competitionSystem, playoff bracket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionSystem Context triple: [Liguilla, competitionSystem, playoff bracket]
-
A.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
competitionClass
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
D.
competitionSeries
Indicates that one entity is a recurring competitive event or series in which the other entity participates or is featured.
-
E.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6ce0538f48190abf3160681901c17 |
completed | March 27, 2026, 6:35 p.m. |
Created at: March 27, 2026, 1:50 p.m.