Triple
T35877163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullens Road |
E1037397
|
entity |
| Predicate | usedOnMatchdaysFor |
P44508
|
FINISHED |
| Object | pedestrian access |
—
|
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: pedestrian access | Statement: [Bullens Road, usedOnMatchdaysFor, pedestrian access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnMatchdaysFor Context triple: [Bullens Road, usedOnMatchdaysFor, pedestrian access]
-
A.
usedInMatchSchedules
Indicates that something (such as a resource, rule, or configuration) is utilized within the scheduling or arrangement of matches.
-
B.
typicalMatchDay
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
C.
usedInFriendlyMatches
Indicates that something (such as a rule, tactic, or item) is employed or applied specifically in the context of friendly (non-competitive) matches.
-
D.
matchdayElement
Indicates a relationship where an element (such as a game, event, or component) is part of or associated with a specific matchday.
-
E.
matchdayActivity
chosen
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.