Triple
T36115967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Cassidy |
E1044614
|
entity |
| Predicate | hasCompetitedIn |
P204737
|
FINISHED |
| Object | Super Formula |
E1044608
|
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: Super Formula | Statement: [Nick Cassidy, hasCompetitedIn, Super Formula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitedIn Context triple: [Nick Cassidy, hasCompetitedIn, Super Formula]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
C.
regionCompetedIn
Indicates the geographic region or area where an entity participated in a competition or contest.
-
D.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
E.
hasCompetitionHistory
Indicates that an entity has a recorded history of participation in competitions or competitive events.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396df4ecec8190af64321f75f03e03 |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.