Triple
T32114418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varda |
E820198
|
entity |
| Predicate | especiallyReveredBy |
P8505
|
FINISHED |
| Object | Eldar |
—
|
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: Eldar | Statement: [Varda, especiallyReveredBy, Eldar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: especiallyReveredBy Context triple: [Varda, especiallyReveredBy, Eldar]
-
A.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
B.
veneratedBy
chosen
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
isVeneratedAs
Indicates that one entity is regarded and honored by others as sacred, holy, or worthy of deep reverence.
-
D.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
E.
veneratedOn
Indicates that an entity is honored, revered, or celebrated on a specific date or occasion.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b906a92c819096335394dd7f767e |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.