Triple
T32025108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishy |
E817796
|
entity |
| Predicate | playsForFederation |
P178090
|
FINISHED |
| Object | All India Chess Federation |
—
|
NE NERFINISHED |
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: All India Chess Federation | Statement: [Vishy, playsForFederation, All India Chess Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsForFederation Context triple: [Vishy, playsForFederation, All India Chess Federation]
-
A.
playsForTitle
Indicates that an entity performs or competes on behalf of a team, organization, or group under a specific title or designation.
-
B.
playsForProvinceOrState
Indicates that an athlete or player is a member of, or represents, a particular provincial or state-level team or organization.
-
C.
teamPlaysIn
Indicates that a specific sports team participates or competes in a particular league, division, or competition.
-
D.
nationalFederationAffiliation
Indicates that one organization is formally affiliated with, or a member of, a specified national federation.
-
E.
stateTeamOf
Indicates that one entity is the official team representing a particular state associated with another entity.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: May 1, 2026, 12:17 a.m.