Triple
T36606672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickel and Dimed |
E903060
|
entity |
| Predicate | featuresJob |
P126481
|
FINISHED |
| Object | waitress |
—
|
LITERAL 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: waitress | Statement: [Nickel and Dimed, featuresJob, waitress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresJob Context triple: [Nickel and Dimed, featuresJob, waitress]
-
A.
featuresTask
Indicates that an entity includes or presents a specific task as one of its components or elements.
-
B.
featuresWorkType
chosen
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
workFeatured
Indicates that one work is highlighted, showcased, or given special prominence within a particular context, collection, or presentation.
-
E.
featuresSign
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
- F. None of above.
Provenance (3 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.