Triple
T32224535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eönwë |
E823158
|
entity |
| Predicate | judged |
P3169
|
FINISHED |
| Object | the claim of the sons of Fëanor to the Silmarils |
—
|
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: the claim of the sons of Fëanor to the Silmarils | Statement: [Eönwë, judged, the claim of the sons of Fëanor to the Silmarils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judged Context triple: [Eönwë, judged, the claim of the sons of Fëanor to the Silmarils]
-
A.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
-
B.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
C.
judgedOn
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
D.
judge
chosen
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
-
E.
judgeFrom
Indicates that one entity forms an opinion, evaluation, or conclusion about something based on another specified source, basis, or perspective.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc8c6c881908ce99e774c010ff5 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.