Triple
T36974306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Lane End |
E914655
|
entity |
| Predicate | boundaryEndOf |
P52351
|
FINISHED |
| Object | cricket field at SuperSport Park |
—
|
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: cricket field at SuperSport Park | Statement: [West Lane End, boundaryEndOf, cricket field at SuperSport Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryEndOf Context triple: [West Lane End, boundaryEndOf, cricket field at SuperSport Park]
-
A.
endBoundaryDefinedBy
chosen
Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by another entity.
-
B.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
boundaryExpression
Indicates a limiting or constraining condition that defines the allowable range, scope, or behavior of something within a system or context.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
rangeEnd
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
- 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.