Triple
T31072025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simdega district |
E791846
|
entity |
| Predicate | hasSignificantSport |
P33270
|
FINISHED |
| Object | field hockey |
—
|
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: field hockey | Statement: [Simdega district, hasSignificantSport, field hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantSport Context triple: [Simdega district, hasSignificantSport, field hockey]
-
A.
hasMajorSport
chosen
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
B.
hasSportsRole
Indicates that an entity holds or is assigned a specific role or position within a sports context or organization.
-
C.
hasChampionshipSport
Indicates that an entity offers, sponsors, or is associated with a particular sport at a championship or competitive level.
-
D.
notableSportIncluded
Indicates that a particular sport is prominently featured or included as a notable component within something, such as an event, program, or context.
-
E.
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.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 9:01 p.m.