Triple
T30972961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courtney Frerichs |
E789146
|
entity |
| Predicate | hasRunningDiscipline |
P115475
|
FINISHED |
| Object | track running |
—
|
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: track running | Statement: [Courtney Frerichs, hasRunningDiscipline, track running]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunningDiscipline Context triple: [Courtney Frerichs, hasRunningDiscipline, track running]
-
A.
hasRacingDiscipline
Indicates that an entity participates in, is associated with, or is characterized by a specific type or category of racing discipline.
-
B.
runningDiscipline
chosen
Indicates a relationship where an entity participates in or is associated with running as a sport or athletic discipline.
-
C.
currentDiscipline
Indicates the disciplinary field or area of study in which an entity is presently engaged or classified.
-
D.
hasDisciplineSystem
Indicates that an entity possesses or is governed by a particular system of rules, methods, or practices for maintaining discipline.
-
E.
hasDisplayDiscipline
Indicates that an entity is associated with a particular academic or professional discipline in which its content is displayed or categorized.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:55 p.m.