Triple
T6142369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beth Riesgraf |
E136990
|
entity |
| Predicate | notableCharacterTraitOfRole |
P37384
|
FINISHED |
| Object | quirky thief Parker on Leverage |
—
|
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: quirky thief Parker on Leverage | Statement: [Beth Riesgraf, notableCharacterTraitOfRole, quirky thief Parker on Leverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterTraitOfRole Context triple: [Beth Riesgraf, notableCharacterTraitOfRole, quirky thief Parker on Leverage]
-
A.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
B.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
C.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
D.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
E.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb387ac8190a60579b59a741425 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.