Triple
T25088101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werther |
E628378
|
entity |
| Predicate | philosophicalTrait |
P37384
|
FINISHED |
| Object | romantic |
—
|
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: romantic | Statement: [Werther, philosophicalTrait, romantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: philosophicalTrait Context triple: [Werther, philosophicalTrait, romantic]
-
A.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
B.
philosophicalTheme
Indicates that a work, idea, or discourse centrally involves or explores a particular philosophical concept, question, or line of thought.
-
C.
성격
Indicates a relationship where one entity’s character, temperament, or personality traits are attributed to or associated with that entity.
-
D.
personalityType
Indicates the specific psychological or behavioral profile that characterizes an entity’s typical patterns of thinking, feeling, and acting.
-
E.
philosophicalConcept
Indicates that one entity is a philosophical concept that characterizes, explains, or is thematically central to the other 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461e667a48190ad63646978cadf62 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:24 a.m.