Triple
T9405620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustav von Aschenbach |
E226578
|
entity |
| Predicate | desireType |
P66260
|
FINISHED |
| Object | homoerotic |
—
|
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: homoerotic | Statement: [Gustav von Aschenbach, desireType, homoerotic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: desireType Context triple: [Gustav von Aschenbach, desireType, homoerotic]
-
A.
wantedBy
Indicates that one entity is desired, sought, or wished for by another entity.
-
B.
hasRepressedDesireFor
chosen
Indicates that one entity harbors a hidden or unacknowledged longing or attraction toward another entity.
-
C.
describesSearchFor
Indicates that one entity provides a description or characterization of another entity’s act of searching for something.
-
D.
seeType
Indicates that one entity observes, recognizes, or visually perceives another entity of a particular type or category.
-
E.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c2b9bc81909a4ce91792294d1c |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.