Triple
T24961811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiff Upper Lip, Jeeves |
E624627
|
entity |
| Predicate | titleCharacterTraitReferenced |
P158727
|
FINISHED |
| Object | British stoicism |
—
|
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: British stoicism | Statement: [Stiff Upper Lip, Jeeves, titleCharacterTraitReferenced, British stoicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterTraitReferenced Context triple: [Stiff Upper Lip, Jeeves, titleCharacterTraitReferenced, British stoicism]
-
A.
hasTitleCharacterTrait
Indicates that a title is associated with a specific character trait of an entity.
-
B.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
C.
childCharacterTrait
Indicates that a child possesses or exhibits a particular character trait.
-
D.
titleCharacterRelation
Indicates the relationship between a work’s title and a specific character it references or centers on.
-
E.
titleCharacterization
chosen
Indicates how a title characterizes, describes, or frames an associated entity (such as a work, person, or concept).
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 5:59 a.m.