Triple
T27600426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Olten |
E700024
|
entity |
| Predicate | hasHomeFansFrom |
P136905
|
FINISHED |
| Object | Olten |
—
|
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: Olten | Statement: [FC Olten, hasHomeFansFrom, Olten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFansFrom Context triple: [FC Olten, hasHomeFansFrom, Olten]
-
A.
hasHomeFans
chosen
Indicates that a team, player, or participant is supported by fans located at their home venue or home location.
-
B.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
C.
hasFanBaseFor
Indicates that an entity has a group of supporters or admirers specifically dedicated to another entity (such as a work, person, or brand).
-
D.
hasHomeFansNickname
Indicates that an entity is known by a particular nickname specifically used by its home fans.
-
E.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 2:08 p.m.