Triple
T28845219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL professional teams |
E728433
|
entity |
| Predicate | leagueStructureLevel |
P50168
|
FINISHED |
| Object | professional tier |
—
|
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: professional tier | Statement: [USL professional teams, leagueStructureLevel, professional tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueStructureLevel Context triple: [USL professional teams, leagueStructureLevel, professional tier]
-
A.
leagueStructure
Indicates how a league is organized, including its divisions, tiers, and the relationships or hierarchy between its constituent groups or competitions.
-
B.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
C.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
D.
stateLeagueLevel
Indicates the competitive tier or division level of a league within a particular state’s league system.
-
E.
levelInNationalTeamStructure
Indicates the hierarchical tier or rank that an entity occupies within a national team’s organizational structure.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 6:42 a.m.