Triple
T23601967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadowbank Stadium |
E582781
|
entity |
| Predicate | openedForDorkingWanderers |
P152883
|
FINISHED |
| Object | late 2010s |
—
|
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: late 2010s | Statement: [Meadowbank Stadium, openedForDorkingWanderers, late 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForDorkingWanderers Context triple: [Meadowbank Stadium, openedForDorkingWanderers, late 2010s]
-
A.
openedToProspectors
Indicates that access or rights to a resource, area, or opportunity have been made available for exploration, evaluation, or exploitation by prospectors.
-
B.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
C.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
E.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0947bd8819097e26643dc257dc0 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:43 p.m.