Triple
T26396366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armadale, West Lothian |
E663567
|
entity |
| Predicate | sportsHosted |
P66209
|
FINISHED |
| Object | speedway |
—
|
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: speedway | Statement: [Armadale, West Lothian, sportsHosted, speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsHosted Context triple: [Armadale, West Lothian, sportsHosted, speedway]
-
A.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
B.
sportsAttraction
chosen
Indicates a relationship where an entity serves as a venue, site, or draw specifically for sports-related activities or events.
-
C.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
D.
cohostedSportingEvents
Indicates that two or more entities jointly organized or hosted one or more sporting events together.
-
E.
tournamentHost
Indicates that one entity serves as the organizer or official host of a tournament involving the other 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:29 p.m.