Triple
T33492994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Decreasing Circles |
E857788
|
entity |
| Predicate | characterTraitOfMartinBryce |
P37384
|
FINISHED |
| Object | obsessive |
—
|
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: obsessive | Statement: [Ever Decreasing Circles, characterTraitOfMartinBryce, obsessive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterTraitOfMartinBryce Context triple: [Ever Decreasing Circles, characterTraitOfMartinBryce, obsessive]
-
A.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
B.
introducesCharacterTrait
Indicates that an entity presents or establishes a new characteristic or quality of a character within a narrative or context.
-
C.
hasPersonalityDescribedAs
Indicates that an entity possesses a personality characterized or labeled in a particular way.
-
D.
secondaryCharacterTrait
Indicates that a secondary or supporting character possesses a particular attribute, quality, or personality trait.
-
E.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:38 a.m.