Triple
T28073946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manjappada |
E709480
|
entity |
| Predicate | supportsPlayerNationality |
P81085
|
FINISHED |
| Object | Indian players |
—
|
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: Indian players | Statement: [Manjappada, supportsPlayerNationality, Indian players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayerNationality Context triple: [Manjappada, supportsPlayerNationality, Indian players]
-
A.
nationalityInPlay
Indicates that, within the context of a play or performance, a character is portrayed as having a particular nationality.
-
B.
supportsNationalTeam
chosen
Indicates that one entity provides backing, endorsement, or assistance to a national team.
-
C.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
D.
hasParticipantNationality
Indicates that a participant in an event, activity, or relation has a specific nationality.
-
E.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: April 27, 2026, 8:47 p.m.