Triple
T28651321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andvari's ring |
E725206
|
entity |
| Predicate | effectOnBearer |
P176310
|
FINISHED |
| Object | brings death |
—
|
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: brings death | Statement: [Andvari's ring, effectOnBearer, brings death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnBearer Context triple: [Andvari's ring, effectOnBearer, brings death]
-
A.
eraOfBearer
Indicates that a time period or era is associated with, or characterizes, the bearer entity.
-
B.
relationViaBearer
Indicates that one entity is related to another indirectly through an intermediate bearer or carrier that holds or mediates the relationship between them.
-
C.
effectOnIssuance
Indicates how one factor or condition influences the issuance or granting of something (such as a document, license, or asset).
-
D.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
E.
notableBearerDescription
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 28, 2026, 4:52 a.m.