Triple
T26327470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statham Stand |
E662291
|
entity |
| Predicate | hasEponymSport |
P5150
|
FINISHED |
| Object | cricket |
—
|
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 | Statement: [Statham Stand, hasEponymSport, cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymSport Context triple: [Statham Stand, hasEponymSport, cricket]
-
A.
hasNameInSport
Indicates that an entity is known by a particular name specifically within the context of a given sport.
-
B.
eponymPlayedFor
Indicates that the eponymous person or entity was a member of, or played for, a particular team or organization.
-
C.
knownForSports
chosen
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
D.
hasEponymConnectionTo
Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
-
E.
hasEponymCategory
Indicates that one entity serves as the namesake or eponym for the category or class represented by the other 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f65f9f48190ba299fb3e435e67a |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:31 p.m.