Triple
T26451354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanark United F.C. |
E665356
|
entity |
| Predicate | homeGroundTown |
P161708
|
FINISHED |
| Object | Lanark |
—
|
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: Lanark | Statement: [Lanark United F.C., homeGroundTown, Lanark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundTown Context triple: [Lanark United F.C., homeGroundTown, Lanark]
-
A.
homeGroundFrom
Indicates that an entity serves as the home ground or primary venue for another entity (such as a team or organization).
-
B.
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.
-
C.
homeGroundAlternateName
Indicates that an alternative or secondary name is used to refer to a particular home ground.
-
D.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
E.
occasionalHomeGroundCity
Indicates that a location serves as a non-primary or infrequent home ground city for an entity, such as a sports team or organization.
- F. None of above. chosen
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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 12:05 a.m.