Triple
T7827958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Cup |
E181292
|
entity |
| Predicate | introducedGroupStage |
P27921
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [AFC Cup, introducedGroupStage, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedGroupStage Context triple: [AFC Cup, introducedGroupStage, 2004]
-
A.
groupStageIntroduced
chosen
Indicates that a group-stage phase was added or implemented in a competition or event format.
-
B.
hasGroupStage
Indicates that an entity includes, participates in, or is associated with a specific group stage within a larger multi-stage structure or process.
-
C.
groupStageGroups
Indicates the grouping of participants or teams into distinct groups within the group stage of a competition or tournament.
-
D.
introducedTeamFeature
Indicates that an entity launched or made available a new feature specifically designed for teams.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a97d748190b1924890b1328bf1 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.