Triple
T12495134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fredrikstad FK |
E298663
|
entity |
| Predicate | homeGroundLocatedOn |
P5282
|
FINISHED |
| Object | eastern bank of Glomma river |
—
|
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: eastern bank of Glomma river | Statement: [Fredrikstad FK, homeGroundLocatedOn, eastern bank of Glomma river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundLocatedOn Context triple: [Fredrikstad FK, homeGroundLocatedOn, eastern bank of Glomma river]
-
A.
homeGroundContext
Indicates the relationship between a sports team and the venue or location that serves as its primary home ground within a given contextual setting.
-
B.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
C.
homeGroundUsedFor
Indicates that a particular venue or stadium is used as the designated home ground for a team, club, or organization.
-
D.
homeFieldLocation
chosen
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
E.
homeGroundFeature
Indicates that a particular feature or characteristic is associated with or defines the home ground of an 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.