Triple
T28984631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBU World Cup |
E734643
|
entity |
| Predicate | hasTeamClassification |
P181746
|
FINISHED |
| Object | Nations Cup |
—
|
NE NERFINISHED |
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: Nations Cup | Statement: [IBU World Cup, hasTeamClassification, Nations Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamClassification Context triple: [IBU World Cup, hasTeamClassification, Nations Cup]
-
A.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
B.
hasNotableTeamType
Indicates that an entity is associated with a team that is recognized as having a specific notable type or category.
-
C.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
D.
hasTeamSide
Indicates that an entity is associated with or belongs to a particular side or faction of a team within a competitive or collaborative context.
-
E.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
- F. None of above. chosen
Provenance (4 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 28, 2026, 9:13 a.m.