Triple
T33229874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowmane |
E850664
|
entity |
| Predicate | associatedWithCharacterDeath |
P17673
|
FINISHED |
| Object | Théoden |
E242439
|
NE 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: Théoden | Statement: [Snowmane, associatedWithCharacterDeath, Théoden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCharacterDeath Context triple: [Snowmane, associatedWithCharacterDeath, Théoden]
-
A.
associatedWithDeathOf
chosen
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
B.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
C.
associatedWithMortal
Indicates a relationship where an entity is connected or linked in some way to a mortal being (a being subject to death).
-
D.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
E.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
- F. None of above.
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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37047ae40081908d4c7bcd95736508 |
completed | June 20, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.