Triple
T35877155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullens Road |
E1037397
|
entity |
| Predicate | usedAsAccessTo |
P41137
|
FINISHED |
| Object | Goodison Park stadium |
—
|
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: Goodison Park stadium | Statement: [Bullens Road, usedAsAccessTo, Goodison Park stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAccessTo Context triple: [Bullens Road, usedAsAccessTo, Goodison Park stadium]
-
A.
usedAsAccessPointForActivity
Indicates that something serves as an access point or entry mechanism through which a particular activity is initiated, enabled, or carried out.
-
B.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
C.
accessedThrough
chosen
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
D.
accessedFor
Indicates that one entity is used to obtain entry to, retrieve, or make use of another entity.
-
E.
usedToAdmit
Indicates that something served as the means or instrument by which an entity was allowed or granted entry or access.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:06 p.m.