Triple
T26827699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fëanor |
E675415
|
entity |
| Predicate | swore |
P1202
|
FINISHED |
| Object | Oath of Fëanor |
—
|
NE NERFINISHED |
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 Fëanor | Statement: [Fëanor, swore, Oath of Fëanor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swore Context triple: [Fëanor, swore, Oath of Fëanor]
-
A.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
-
B.
hasSwornType
Indicates that one entity has formally pledged or committed to a specific type, category, or classification of something.
-
C.
oath
chosen
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.
-
D.
sworeInAs
Indicates that one entity formally administered or participated in the official oath-taking that installed another entity into an office, role, or position.
-
E.
hasSwornStatus
Indicates that an entity is formally bound by an oath or sworn commitment, reflecting an official or pledged status in relation to another entity or role.
- F. None of above.
Provenance (3 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61ada00d48190b6f4c52e6bd33789 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:59 a.m.