Triple
T14435958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division II |
E357960
|
entity |
| Predicate | levelRelativeToMLS |
P13247
|
FINISHED |
| Object | below Major League Soccer |
—
|
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: below Major League Soccer | Statement: [Division II, levelRelativeToMLS, below Major League Soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelRelativeToMLS Context triple: [Division II, levelRelativeToMLS, below Major League Soccer]
-
A.
leagueLevelRelativeToNASL
Indicates the comparative competitive tier or status of a league in relation to the NASL (North American Soccer League).
-
B.
levelInNorthAmericanSystem
Indicates that an entity’s level or grade is defined according to the standards or structure used in the North American system.
-
C.
stateLeagueLevel
Indicates the competitive tier or division level of a league within a particular state’s league system.
-
D.
matchLevel
Indicates the degree or extent to which two entities correspond, align, or are compatible with each other.
-
E.
levelInMinorLeagues
chosen
Indicates the competitive tier or rank at which an entity participates within the minor league system.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.