Triple
T20251414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICTFC |
E498563
|
entity |
| Predicate | homeStadiumSituatedOn |
P139402
|
FINISHED |
| Object | banks of the River Ness |
—
|
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: banks of the River Ness | Statement: [ICTFC, homeStadiumSituatedOn, banks of the River Ness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumSituatedOn Context triple: [ICTFC, homeStadiumSituatedOn, banks of the River Ness]
-
A.
homeStadiumLocatedIn
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
-
B.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
C.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
D.
homeStadiumAlsoKnownAs
Indicates that an alternative or alias name is used for a stadium that serves as a team's home venue.
-
E.
homeStadiumConstructed
Indicates that a particular stadium was built or constructed specifically to serve as the home venue for a given 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a8b8488190b344df7a65f59684 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:41 p.m.