Triple
T33613159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Meares |
E861042
|
entity |
| Predicate | returnedToCompetitionAfterInjury |
P185680
|
FINISHED |
| Object | 2008 neck fracture |
—
|
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: 2008 neck fracture | Statement: [Anna Meares, returnedToCompetitionAfterInjury, 2008 neck fracture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToCompetitionAfterInjury Context triple: [Anna Meares, returnedToCompetitionAfterInjury, 2008 neck fracture]
-
A.
returnedToCompetition
Indicates that an entity resumed participating in a competition after having previously stopped or been absent.
-
B.
returnedToPlayAfterIllness
Indicates that an entity resumed participating in play or competition after having been sidelined due to an illness.
-
C.
returnedToFootball
Indicates that an entity resumed participating in football after having previously stopped or taken a break.
-
D.
namedAfterCompetition
Indicates that one entity receives its name from a specific competition or contest.
-
E.
retiredFromEligibleCompetition
Indicates that an entity has permanently withdrawn from participation in competitions for which they were previously eligible.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 1:41 a.m.