Triple
T13976910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yellow Army |
E336209
|
entity |
| Predicate | nicknameOfTeamFans |
P49044
|
FINISHED |
| Object | Chennai Super Kings fans |
—
|
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: Chennai Super Kings fans | Statement: [The Yellow Army, nicknameOfTeamFans, Chennai Super Kings fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfTeamFans Context triple: [The Yellow Army, nicknameOfTeamFans, Chennai Super Kings fans]
-
A.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
B.
hasHomeFansNickname
Indicates that an entity is known by a particular nickname specifically used by its home fans.
-
C.
supporterGroupNickname
chosen
Indicates that a particular nickname is used to refer to a group of supporters associated with an entity.
-
D.
teamNickname
Indicates the commonly used informal or symbolic name by which a team is known.
-
E.
fanNicknameForFixture
Indicates that a particular nickname is used by fans to refer to a specific fixture or matchup.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e90dc148190b38e339aac0de484 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.