Triple
T11292795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Wise |
E267368
|
entity |
| Predicate | disciplinedSpecialty |
P466
|
FINISHED |
| Object | halfpipe |
—
|
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: halfpipe | Statement: [David Wise, disciplinedSpecialty, halfpipe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplinedSpecialty Context triple: [David Wise, disciplinedSpecialty, halfpipe]
-
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.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
E.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e989fdac81909a4a75f1f68b55c6 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.