Triple
T37490877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caranthir |
E931683
|
entity |
| Predicate | oathSworn |
P9420
|
FINISHED |
| Object | Oath of Fëanor |
E901195
|
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 Fëanor | Statement: [Caranthir, oathSworn, Oath of Fëanor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathSworn Context triple: [Caranthir, oathSworn, Oath of Fëanor]
-
A.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
B.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
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.
-
D.
oathTakenBy
chosen
Indicates that an oath or formal promise has been made by a specific entity.
-
E.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c48a47c819090223d8014e32773 |
completed | June 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.