Triple
T36226542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finrod Felagund |
E891114
|
entity |
| Predicate | keptOathBy |
P184782
|
FINISHED |
| Object | accompanying Beren on his quest |
—
|
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: accompanying Beren on his quest | Statement: [Finrod Felagund, keptOathBy, accompanying Beren on his quest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptOathBy Context triple: [Finrod Felagund, keptOathBy, accompanying Beren on his quest]
-
A.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
brokeOathTo
Indicates that one entity violated or failed to honor a sworn promise or commitment made to another entity.
-
D.
hasSpecialVowOfObedienceRegarding
Indicates that one entity is bound by a distinct or additional vow to obey the authority, directives, or will of another specific entity.
-
E.
penaltyForBreakingOath
Indicates the punishment or negative consequence imposed when an oath is violated.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.