Triple
T36974309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperSport Park |
E914655
|
entity |
| Predicate | hasBoundaryEnd |
P52351
|
FINISHED |
| Object | West Lane End |
—
|
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: West Lane End | Statement: [SuperSport Park, hasBoundaryEnd, West Lane End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryEnd Context triple: [SuperSport Park, hasBoundaryEnd, West Lane End]
-
A.
endBoundaryDefinedBy
chosen
Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by another entity.
-
B.
hasBoundaryIncludes
Indicates that the spatial or conceptual boundary of one entity encompasses or contains the boundary of another entity.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
E.
hasBoundaryValues
Indicates that one entity specifies the limiting or extreme values that define the permissible range or boundary conditions of another 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:14 p.m.