Triple
T37378403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paths of the Dead |
E928358
|
entity |
| Predicate | relatedToVow |
P37
|
FINISHED |
| Object | Oath of the Men of the Mountains |
E2224021
|
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: Oath of the Men of the Mountains | Statement: [Paths of the Dead, relatedToVow, Oath of the Men of the Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToVow Context triple: [Paths of the Dead, relatedToVow, Oath of the Men of the Mountains]
-
A.
associatedVow
Indicates a relationship where a vow is linked or connected to a particular entity or event.
-
B.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
C.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
E.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4076f701f8819088bc2e76a4bada07 |
completed | June 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.