Triple
T37159311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterling Cooper |
E920601
|
entity |
| Predicate | hasCopywriter |
P82050
|
FINISHED |
| Object | Peggy Olson |
E268670
|
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: Peggy Olson | Statement: [Sterling Cooper, hasCopywriter, Peggy Olson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCopywriter Context triple: [Sterling Cooper, hasCopywriter, Peggy Olson]
-
A.
copywriter
chosen
Indicates that one entity serves as a copywriter for another, typically creating written promotional or marketing content on its behalf.
-
B.
hasWriterOfWork
Indicates that a person or entity is the writer/author who created a particular work (such as a book, article, or script).
-
C.
composerOfTextSetting
Indicates that one entity is the composer who created the musical setting for a text associated with another entity.
-
D.
actuallyWrittenBy
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
-
E.
hasNotableWriter
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40360b7c388190885e2db6a514d1b2 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.