Triple
T17965394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyla Ross |
E449190
|
entity |
| Predicate | disciplineSpecialty |
P466
|
FINISHED |
| Object | uneven bars |
—
|
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: uneven bars | Statement: [Kyla Ross, disciplineSpecialty, uneven bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineSpecialty Context triple: [Kyla Ross, disciplineSpecialty, uneven bars]
-
A.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
B.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
C.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
-
D.
institutionSpecialization
Indicates that an institution focuses on, is dedicated to, or has expertise in a particular field, domain, or area of activity.
-
E.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b136e4088190ac97fd92dc84a4b9 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.