Triple
T32193721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Carter |
E822341
|
entity |
| Predicate | notableObjectOfObsession |
P206225
|
FINISHED |
| Object | Mystic Seer napkin-holder machine |
E822345
|
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: Mystic Seer napkin-holder machine | Statement: [Don Carter, notableObjectOfObsession, Mystic Seer napkin-holder machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableObjectOfObsession Context triple: [Don Carter, notableObjectOfObsession, Mystic Seer napkin-holder machine]
-
A.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
B.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
C.
favoriteObject
Indicates that one entity is the preferred or most liked object of another entity.
-
D.
notableArtifactPursued
Indicates that an entity actively seeks, hunts for, or attempts to obtain a particular notable artifact.
-
E.
notableObjectOfStudy
Indicates that a subject is a significant or prominent focus of research, analysis, or scholarly attention for another entity.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bec98288190b1480ba26b1e4eb6 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:35 a.m.