Triple
T36925278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seavey Kennel |
E913325
|
entity |
| Predicate | hasNotableMusher |
P205640
|
FINISHED |
| Object | Mitch Seavey |
E266018
|
NE 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: Mitch Seavey | Statement: [Seavey Kennel, hasNotableMusher, Mitch Seavey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMusher Context triple: [Seavey Kennel, hasNotableMusher, Mitch Seavey]
-
A.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
B.
hadNotableRider
Indicates that an animal, vehicle, or conveyance was ridden by a person considered historically or culturally notable.
-
C.
hasReindeerHerding
Indicates that one entity engages in or possesses the activity, practice, or operation of herding reindeer in relation to another entity.
-
D.
hasNotableJockey
Indicates that an entity (typically a racehorse) is or was ridden by a jockey who is considered notable or distinguished.
-
E.
hasNotableContestant
Indicates that an entity (such as a competition, show, or event) includes or is associated with a contestant who is notable or distinguished in some way.
- F. None of above. chosen
Provenance (5 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efda85a748190a6ee43529b23fb3a |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.