Triple
T13540631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Dawn |
E323372
|
entity |
| Predicate | titleCharacterDescription |
P32702
|
FINISHED |
| Object | faded Southern belle |
—
|
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: faded Southern belle | Statement: [Delta Dawn, titleCharacterDescription, faded Southern belle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterDescription Context triple: [Delta Dawn, titleCharacterDescription, faded Southern belle]
-
A.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
B.
characterDescription
chosen
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
C.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
titleCharacterNamedAfter
Indicates that a work’s title character is named after, or shares their name with, another specific entity.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd8ba10819098faadcc6adf251e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.