Triple
T35831851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion (Malmö) |
E1035818
|
entity |
| Predicate | hasHomeClubFullName |
P149225
|
FINISHED |
| Object | Malmö Fotbollförening |
—
|
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: Malmö Fotbollförening | Statement: [Stadion (Malmö), hasHomeClubFullName, Malmö Fotbollförening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeClubFullName Context triple: [Stadion (Malmö), hasHomeClubFullName, Malmö Fotbollförening]
-
A.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
B.
homeClubFullName
chosen
Indicates the full official name of the club that serves as the home team in the given context.
-
C.
clubFullName
Indicates the complete official name of a club as opposed to an abbreviation or short form.
-
D.
supportsClubFullName
Indicates that one entity provides backing, endorsement, or assistance to a sports club identified by its full official name.
-
E.
associatedClubCommonName
Indicates that there is a relationship linking an entity to the commonly used or popular name of a club with which it is associated.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:06 p.m.