Triple
T765069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Athena Nike |
E16156
|
entity |
| Predicate | patronDeityFunction |
P9989
|
FINISHED |
| Object | war and victory |
—
|
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: war and victory | Statement: [Temple of Athena Nike, patronDeityFunction, war and victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronDeityFunction Context triple: [Temple of Athena Nike, patronDeityFunction, war and victory]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by another entity.
-
C.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
D.
typeOfDeity
chosen
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a69dfeb08190b54a476cfa66e6d6 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.