Triple
T25221337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reigart Stadium |
E631971
|
entity |
| Predicate | homeClubLeagueSystem |
P158791
|
FINISHED |
| Object | Scottish football league system |
—
|
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: Scottish football league system | Statement: [The Reigart Stadium, homeClubLeagueSystem, Scottish football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeClubLeagueSystem Context triple: [The Reigart Stadium, homeClubLeagueSystem, Scottish football league system]
-
A.
tenantClubLeague
Indicates that a club participates as a tenant (home user of facilities) in a particular league.
-
B.
homeLeagueClub
Indicates that a club competes in or is affiliated with a particular home league.
-
C.
hostLeague
Indicates that one entity serves as the organizing league or governing competition framework for another entity, such as a team or event.
-
D.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular league.
-
E.
homeLeagueOf
Indicates that a league is the primary or official league in which a team or club regularly competes.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:03 p.m.