Triple
T37227720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Pat Pending |
E923047
|
entity |
| Predicate | hasCompetitionWith |
P748
|
FINISHED |
| Object | Dick Dastardly |
E923041
|
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: Dick Dastardly | Statement: [Professor Pat Pending, hasCompetitionWith, Dick Dastardly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionWith Context triple: [Professor Pat Pending, hasCompetitionWith, Dick Dastardly]
-
A.
hasCompetition
chosen
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.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
C.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40637db908819099c0bdbde51e760f |
completed | June 27, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.