Triple
T31520488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhinemaidens |
E804192
|
entity |
| Predicate | finalAppearanceContext |
P77621
|
FINISHED |
| Object | return of the Ring to the Rhine |
—
|
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: return of the Ring to the Rhine | Statement: [Rhinemaidens, finalAppearanceContext, return of the Ring to the Rhine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAppearanceContext Context triple: [Rhinemaidens, finalAppearanceContext, return of the Ring to the Rhine]
-
A.
finalAppearanceIn
chosen
Indicates that an entity makes its last or final appearance within a specified work, episode, or context.
-
B.
typicalAppearanceContext
Indicates the usual situation, setting, or context in which an entity most commonly appears or is typically encountered.
-
C.
coreAppearance
Indicates that one entity serves as the primary or defining visual form or look of another entity.
-
D.
finalPhaseOutContext
Indicates the context or circumstances under which something is in its final stage of being phased out or discontinued.
-
E.
returnAppearance
Indicates that one entity resumes or restores a previous visual form, style, or outward appearance of another entity or of itself.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 30, 2026, 9:55 p.m.