Triple
T32096793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame of Udûn |
E819740
|
entity |
| Predicate | associatedWithMaster |
P206184
|
FINISHED |
| Object | Morgoth |
E261179
|
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: Morgoth | Statement: [Flame of Udûn, associatedWithMaster, Morgoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMaster Context triple: [Flame of Udûn, associatedWithMaster, Morgoth]
-
A.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
B.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
-
C.
associatedWithStand
Indicates a relationship where an entity is linked or connected to a particular stand, such as being located at, operating in, or otherwise related to that stand.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
- F. None of above. chosen
Provenance (5 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3542f88f708190b88cf4e5ba317fe8 |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:26 a.m.