Triple
T31885343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team England |
E813992
|
entity |
| Predicate | athleteSelectionFor |
P31058
|
FINISHED |
| Object | Commonwealth Games |
—
|
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: Commonwealth Games | Statement: [Team England, athleteSelectionFor, Commonwealth Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athleteSelectionFor Context triple: [Team England, athleteSelectionFor, Commonwealth Games]
-
A.
athleteSelectionLevel
Indicates the stage or tier at which an athlete has been chosen or qualified within a selection or ranking process.
-
B.
teamSelection
chosen
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
C.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
D.
athleteRecruitmentFrom
Indicates that an athlete was recruited from a particular source, such as a school, team, or location.
-
E.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0daa4988190b78498e7da6a30dd |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:57 p.m.