Triple
T30624327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamadutas |
E779530
|
entity |
| Predicate | associatedWithTextTheme |
P176949
|
FINISHED |
| Object | descriptions_of_hellish_planets |
—
|
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: descriptions_of_hellish_planets | Statement: [Yamadutas, associatedWithTextTheme, descriptions_of_hellish_planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTextTheme Context triple: [Yamadutas, associatedWithTextTheme, descriptions_of_hellish_planets]
-
A.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
B.
coreThemeAssociation
chosen
Indicates a primary, central, or defining thematic relationship between two entities, where one serves as a core theme of the other.
-
C.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
-
D.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
E.
alignmentTheme
Indicates that one entity serves as the central topic, focus, or thematic basis for the alignment or correspondence expressed by another 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:27 p.m.