Triple
T7427340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Super League |
E171400
|
entity |
| Predicate | hasYouthDevelopmentPrograms |
P6626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Indian Super League, hasYouthDevelopmentPrograms, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthDevelopmentPrograms Context triple: [Indian Super League, hasYouthDevelopmentPrograms, yes]
-
A.
hasYouthProgram
chosen
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
B.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
C.
youthAcademyFocus
Indicates that an organization or program is primarily dedicated to developing and training young or junior participants.
-
D.
hasCadetProgram
Indicates that an organization or entity offers or operates a cadet program for training or development.
-
E.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3055b7881908269ab909c5a85b5 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.