Triple
T29280777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Dustland Fairytale |
E742370
|
entity |
| Predicate | featuresCharacterArchetype |
P102015
|
FINISHED |
| Object | princess |
—
|
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: princess | Statement: [A Dustland Fairytale, featuresCharacterArchetype, princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterArchetype Context triple: [A Dustland Fairytale, featuresCharacterArchetype, princess]
-
A.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
B.
usesCharacterArchetype
chosen
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
featuresPsychicCharacter
Indicates that the subject includes or involves a character who possesses psychic or telepathic abilities.
-
E.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: April 28, 2026, 12:54 p.m.