Triple
T29679763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEI Nations Cup |
E750917
|
entity |
| Predicate | teamSelectionBy |
P75565
|
FINISHED |
| Object | national equestrian federations |
—
|
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: national equestrian federations | Statement: [FEI Nations Cup, teamSelectionBy, national equestrian federations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSelectionBy Context triple: [FEI Nations Cup, teamSelectionBy, national equestrian federations]
-
A.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
B.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
C.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
D.
AllWNBATeamSelection
Indicates that a player has been selected to an All-WNBA Team for a given season or time period.
-
E.
squadSelectionBasis
chosen
Indicates the criterion or rationale used to choose which individuals are included in a particular squad or team.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672608bf8819092efc616e42a361b |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:09 p.m.