Triple
T36974307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Lane End |
E914655
|
entity |
| Predicate | namedEndOf |
P48547
|
FINISHED |
| Object | SuperSport Park cricket ground |
—
|
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: SuperSport Park cricket ground | Statement: [West Lane End, namedEndOf, SuperSport Park cricket ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedEndOf Context triple: [West Lane End, namedEndOf, SuperSport Park cricket ground]
-
A.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
-
B.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
C.
nameOfEndAt
Indicates that something has the specified name at the point or time when it ends.
-
D.
nameEnding
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
E.
notablePositionEnd
Indicates the point in time or event at which an entity’s notable position, role, or office comes to an end.
- 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_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:14 p.m.