Triple
T33946086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLR |
E870292
|
entity |
| Predicate | hasExpansionTeams |
P186762
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MLR, hasExpansionTeams, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionTeams Context triple: [MLR, hasExpansionTeams, yes]
-
A.
expansionTeamsAdded
chosen
Indicates that new expansion teams have been added to an existing league, organization, or competition.
-
B.
expansionTeamIn
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
C.
expandedFromTeams
Indicates that something has been enlarged, extended, or developed starting from one or more teams as the original basis.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
expansionTeamWith
Indicates that one entity is an expansion team associated with, or added to, another entity such as a league, division, or organization.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:49 a.m.