Triple
T24916788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Stand |
E624009
|
entity |
| Predicate | partOfHomeStadiumOf |
P83131
|
FINISHED |
| Object | Greenock Morton 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: Greenock Morton F.C. | Statement: [Main Stand, partOfHomeStadiumOf, Greenock Morton F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHomeStadiumOf Context triple: [Main Stand, partOfHomeStadiumOf, Greenock Morton F.C.]
-
A.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
B.
homeStadiumOfOtherParticipant
chosen
Indicates that a stadium serves as the home venue for another participant (such as a team or club) involved in an event or competition.
-
C.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
D.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
homeStadiumLocatedIn
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:28 a.m.