Triple
T22074347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irani Cup |
E545485
|
entity |
| Predicate | opponentTeamType |
P54987
|
FINISHED |
| Object | composite team |
—
|
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: composite team | Statement: [Irani Cup, opponentTeamType, composite team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTeamType Context triple: [Irani Cup, opponentTeamType, composite team]
-
A.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
-
B.
opponentStarPlayerTeam
Indicates that the referenced team is the one for which the opponent’s star player plays.
-
C.
featuresOpponentType
chosen
Indicates that an entity involves, includes, or is associated with an opponent of a specified type within a competitive or adversarial context.
-
D.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
E.
opponentTeamsAffected
Indicates that the specified action, condition, or effect applies to the teams designated as opponents.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.