Triple
T3282856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Ashes |
E68911
|
entity |
| Predicate | representsForCharacters |
P47686
|
FINISHED |
| Object | the cost of others’ luxury |
—
|
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: the cost of others’ luxury | Statement: [Valley of Ashes, representsForCharacters, the cost of others’ luxury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsForCharacters Context triple: [Valley of Ashes, representsForCharacters, the cost of others’ luxury]
-
A.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
B.
representsPeople
Indicates that one entity serves as a representation or stand-in for one or more people.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
E.
representsNickname
Indicates that one entity serves as a nickname or informal alternative name for another entity.
- F. None of above. chosen
Provenance (4 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0345d448190a1f936abe7748e33 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.