Triple
T19981461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Senior |
E493823
|
entity |
| Predicate | speaksFamousLines |
P84993
|
FINISHED |
| Object | “Sweet are the uses of adversity” |
—
|
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: “Sweet are the uses of adversity” | Statement: [Duke Senior, speaksFamousLines, “Sweet are the uses of adversity”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speaksFamousLines Context triple: [Duke Senior, speaksFamousLines, “Sweet are the uses of adversity”]
-
A.
famousLineSpeaker
chosen
Indicates that the subject is the person who spoke or delivered the famous line referenced by the object.
-
B.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
-
C.
speaksInFilm
Indicates that a person or character provides spoken dialogue or voice work within a particular film.
-
D.
madeFamousByFilm
Indicates that something became widely known or gained significant public recognition as a result of being featured in a film.
-
E.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d13a8a88190bf5f4f697793f4c9 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.