Triple
T3947996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI ProTeams (by invitation) |
E84792
|
entity |
| Predicate | typicalObjective |
P12230
|
FINISHED |
| Object | promotion to UCI WorldTeam status |
—
|
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: promotion to UCI WorldTeam status | Statement: [UCI ProTeams (by invitation), typicalObjective, promotion to UCI WorldTeam status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalObjective Context triple: [UCI ProTeams (by invitation), typicalObjective, promotion to UCI WorldTeam status]
-
A.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
-
B.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
D.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
E.
trainingObjective
Indicates the goal or target outcome that a training process is designed to achieve.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.