Triple
T31674603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperLiga |
E808364
|
entity |
| Predicate | involvedLeague |
P107979
|
FINISHED |
| Object | Major League Soccer |
—
|
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: Major League Soccer | Statement: [SuperLiga, involvedLeague, Major League Soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedLeague Context triple: [SuperLiga, involvedLeague, Major League Soccer]
-
A.
leagueInvolvement
chosen
Indicates that an entity participates in, is affiliated with, or is otherwise involved in a particular league.
-
B.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
C.
integratedLeague
Indicates that previously separate or segregated leagues have been combined into a single, unified league structure.
-
D.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
E.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 30, 2026, 11:02 p.m.