Triple
T28219945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neville Bowles Chamberlain |
E711423
|
entity |
| Predicate | sportInvented |
P126580
|
FINISHED |
| Object | snooker |
—
|
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: snooker | Statement: [Neville Bowles Chamberlain, sportInvented, snooker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportInvented Context triple: [Neville Bowles Chamberlain, sportInvented, snooker]
-
A.
introducedSport
Indicates that an entity caused a particular sport to be brought into use, practice, or awareness within a specific context or place.
-
B.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
-
C.
sportCreated
chosen
Indicates that an entity is the originator or inventor of a particular sport.
-
D.
originalSport
Indicates that one sport is the initial or primary sport associated with an entity, often before any change, adaptation, or transition to another sport.
-
E.
inSportHistory
Indicates that an entity is recorded or recognized as part of the historical events, records, or legacy of a particular sport.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 10:45 p.m.