Triple
T23981088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa MX Femenil |
E604508
|
entity |
| Predicate | participantLeague |
P21421
|
FINISHED |
| Object | Liga MX Femenil |
—
|
NE NERFINISHED |
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: Liga MX Femenil | Statement: [Copa MX Femenil, participantLeague, Liga MX Femenil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantLeague Context triple: [Copa MX Femenil, participantLeague, Liga MX Femenil]
-
A.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
B.
isPartOfLeague
chosen
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
C.
leagueParticipations
Indicates participation relationships where an entity takes part in one or more leagues or league seasons.
-
D.
leagueInvolvement
Indicates that an entity participates in, is affiliated with, or is otherwise involved in a particular league.
-
E.
employerLeague
Indicates that an organization or entity serves as the employing league or governing competition body for another entity (such as a team or participant).
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2be350c8190a0f8937094f4a902 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:27 p.m.