Triple
T35831843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion (Malmö) |
E1035818
|
entity |
| Predicate | hasMainTenantLeague |
P62954
|
FINISHED |
| Object | Allsvenskan |
E315557
|
NE 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: Allsvenskan | Statement: [Stadion (Malmö), hasMainTenantLeague, Allsvenskan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTenantLeague Context triple: [Stadion (Malmö), hasMainTenantLeague, Allsvenskan]
-
A.
hasPrimaryTenantCompetition
Indicates that an entity’s main tenant faces direct competitive pressure from another tenant or business.
-
B.
hasMajorDomesticLeague
Indicates that an entity possesses or is associated with a primary, top-tier domestic sports league within its jurisdiction.
-
C.
isTopLevelLeagueIn
Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
-
D.
soccerTenantLeague
chosen
Indicates that a soccer tenant (such as a club or team) participates in or is affiliated with a particular soccer league.
-
E.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
- F. None of above.
Provenance (4 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0301c45274819083b0dd9d335f7ee0 |
completed | May 12, 2026, 10:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4df05988190a6bec3993b633b3a |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a03015c272481908a7bfe81befb1764 |
completed | May 12, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:06 p.m.