Triple
T1493186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carry On, Jeeves |
E29626
|
entity |
| Predicate | hasSupportingCharacterTrait |
P28619
|
FINISHED |
| Object | unflappable |
—
|
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: unflappable | Statement: [Carry On, Jeeves, hasSupportingCharacterTrait, unflappable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportingCharacterTrait Context triple: [Carry On, Jeeves, hasSupportingCharacterTrait, unflappable]
-
A.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
B.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
C.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
D.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
-
E.
logicalTrait
Indicates that an entity possesses a characteristic, behavior, or quality related to logical reasoning or structured thinking.
- F. None of above. chosen
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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c665488190ae665f7a1b0563f5 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.