Triple
T26099721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavilion End |
E658362
|
entity |
| Predicate | hasBowlingDirection |
P166141
|
FINISHED |
| Object | from pavilion side towards Vauxhall End |
—
|
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: from pavilion side towards Vauxhall End | Statement: [Pavilion End, hasBowlingDirection, from pavilion side towards Vauxhall End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBowlingDirection Context triple: [Pavilion End, hasBowlingDirection, from pavilion side towards Vauxhall End]
-
A.
hasBowlingBrand
Indicates that one entity is associated with or uses a particular bowling-related brand.
-
B.
bowlingStrength
Indicates the degree or effectiveness of one entity’s bowling performance or capability in relation to another.
-
C.
bowlingCoach
Indicates that one entity serves as a coach or instructor for another entity specifically in the sport of bowling.
-
D.
associatedWithBowlingStyleOfPerson
Indicates a relationship where something is linked to or characterized by the specific bowling style used by a person.
-
E.
bowlingPace
Indicates the speed at which a bowler delivers the ball in cricket.
- F. None of above. chosen
Provenance (4 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 26, 2026, 7:54 p.m.