Triple
T30779159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican National Trios Championship |
E783761
|
entity |
| Predicate | isTriosTitle |
P134745
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mexican National Trios Championship, isTriosTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTriosTitle Context triple: [Mexican National Trios Championship, isTriosTitle, true]
-
A.
isByTrioFrontedBy
Indicates that something (typically a work or performance) is created or performed by a trio that is led or fronted by a particular person or entity.
-
B.
hasTriosChampionship
chosen
Indicates that an entity holds or has held a championship title specifically contested by teams of three members.
-
C.
hasWomenTagOrTriosLikeTitle
Indicates that the item’s title suggests it involves women or trio-related content, based on specific tags or title patterns.
-
D.
hasTrilogy
Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
-
E.
isTitleTrack
Indicates that a song or track shares the same title as the album, film, or larger work it belongs to.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe367d8819088c30ff3cb3866bb |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.