Triple
T24318622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copland Road Stand |
E612892
|
entity |
| Predicate | homeSupportersSectionOf |
P42456
|
FINISHED |
| Object | Rangers F.C. |
—
|
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: Rangers F.C. | Statement: [Copland Road Stand, homeSupportersSectionOf, Rangers F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSupportersSectionOf Context triple: [Copland Road Stand, homeSupportersSectionOf, Rangers F.C.]
-
A.
homeSupportersSectionFor
chosen
Indicates that a particular seating section is designated for the home team's supporters at a sporting event or venue.
-
B.
hasSupportersSection
Indicates that something includes a dedicated section or area specifically intended for its supporters.
-
C.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
D.
homeSectionName
Indicates the designated name or label assigned to a particular section of a home or homepage.
-
E.
supportsSection
Indicates that one entity provides structural or functional backing or reinforcement to a specific section 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:47 a.m.