Triple
T7917603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barisal |
E183865
|
entity |
| Predicate | hasSportsActivity |
P78147
|
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: [Barisal, hasSportsActivity, cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsActivity Context triple: [Barisal, hasSportsActivity, cricket]
-
A.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
B.
hasLocalSport
chosen
Indicates that a place or community is associated with, supports, or regularly engages in a particular sport at the local level.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
E.
hasSportsBody
Indicates that an entity possesses a body or physique that is characteristic of someone who regularly engages in sports or athletic activities.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8e8b388190b5544eb5b8159e07 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.