Triple
T6419883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludi Apollinares |
E127917
|
entity |
| Predicate | deityAspectHonored |
P69432
|
FINISHED |
| Object | Apollo as a healing god |
—
|
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: Apollo as a healing god | Statement: [Ludi Apollinares, deityAspectHonored, Apollo as a healing god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityAspectHonored Context triple: [Ludi Apollinares, deityAspectHonored, Apollo as a healing god]
-
A.
honorsDeityAs
chosen
Indicates that one entity venerates, worships, or regards another entity as a particular deity or divine figure.
-
B.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
-
C.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690194dc8190b3382bd5f92876b5 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.