Triple
T28696385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Ewald the Black |
E729427
|
entity |
| Predicate | veneratedAlongside |
P23286
|
FINISHED |
| Object | Saint Ewald the Fair |
—
|
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: Saint Ewald the Fair | Statement: [Saint Ewald the Black, veneratedAlongside, Saint Ewald the Fair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedAlongside Context triple: [Saint Ewald the Black, veneratedAlongside, Saint Ewald the Fair]
-
A.
worshippedAlongside
chosen
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
-
B.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
unitesVenerationOf
Indicates that one entity brings together or combines the acts or practices of veneration directed toward multiple entities into a unified form.
-
D.
veneratedOn
Indicates that an entity is honored, revered, or celebrated on a specific date or occasion.
-
E.
isVeneratedAs
Indicates that one entity is regarded and honored by others as sacred, holy, or worthy of deep reverence.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656af1dec8190a5ad3298de3cb914 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:39 a.m.