Triple
T549483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Scarlet Letter |
E11805
|
entity |
| Predicate | notableMotif |
P7671
|
FINISHED |
| Object | scaffold scenes |
—
|
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: scaffold scenes | Statement: [The Scarlet Letter, notableMotif, scaffold scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMotif Context triple: [The Scarlet Letter, notableMotif, scaffold scenes]
-
A.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
B.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
C.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49901e4e481909a5ed93c21ab37bd |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.