Triple
T34728650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreis |
E1001142
|
entity |
| Predicate | hasNotablePersonInSports |
P94555
|
FINISHED |
| Object | Jason Kreis |
E304312
|
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: Jason Kreis | Statement: [Kreis, hasNotablePersonInSports, Jason Kreis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePersonInSports Context triple: [Kreis, hasNotablePersonInSports, Jason Kreis]
-
A.
notableAthleteFrom
chosen
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
B.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
C.
notableCharacterSport
Indicates that a notable character is associated with, participates in, or is prominently linked to a particular sport.
-
D.
knownForSports
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
E.
hasNotableSportAlumnus
Indicates that an institution or organization has at least one alumnus who is notable for achievements in sports.
- F. None of above.
Provenance (4 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a033ed9322c8190be994a8d99761caa |
completed | May 12, 2026, 2:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376626c5f4819099d509dd203b7564 |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a033df2b254819082a672859e5168e6 |
completed | May 12, 2026, 2:49 p.m. |
Created at: May 3, 2026, 3:59 p.m.