Triple
T36390907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobs Worth |
E896323
|
entity |
| Predicate | disciplineDetail |
P25609
|
FINISHED |
| Object | jump racing |
—
|
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: jump racing | Statement: [Bobs Worth, disciplineDetail, jump racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineDetail Context triple: [Bobs Worth, disciplineDetail, jump racing]
-
A.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
-
B.
typeDiscipline
chosen
Indicates that an entity is associated with, categorized under, or characterized by a particular discipline or field of study.
-
C.
disciplineCode
Indicates the specific field, subject area, or branch of study/classification to which an entity is assigned or categorized.
-
D.
disciplineGroupOf
Indicates that one entity is a discipline group to which another entity (such as a person, course, or activity) belongs or is associated.
-
E.
disciplineStrength
Indicates the degree or intensity of self-control or disciplined behavior an entity exhibits in its actions or decisions.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.