Triple
T33895787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raelene Boyle |
E868904
|
entity |
| Predicate | competedInEventCategory |
P37610
|
FINISHED |
| Object | Olympic 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: Olympic Games | Statement: [Raelene Boyle, competedInEventCategory, Olympic Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInEventCategory Context triple: [Raelene Boyle, competedInEventCategory, Olympic Games]
-
A.
competedInCategoryWith
Indicates that two or more entities participated in the same competitive category or division within a contest or event.
-
B.
hasCompetitionCategory
Indicates that an entity is associated with a specific category or division within a competition.
-
C.
competedInDiscipline
chosen
Indicates that an entity took part in a competition or event within a specific discipline or category.
-
D.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
E.
competitorCategory
Indicates that two entities operate in the same competitive category or market segment, positioning them as rivals within that domain.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:48 a.m.