Triple
T21613962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krios |
E533383
|
entity |
| Predicate | opponentInTitanomachy |
P58158
|
FINISHED |
| Object | Olympian gods |
—
|
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: Olympian gods | Statement: [Krios, opponentInTitanomachy, Olympian gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInTitanomachy Context triple: [Krios, opponentInTitanomachy, Olympian gods]
-
A.
sideTakenInTitanomachy
Indicates which faction or side an entity aligned with or supported during the Titanomachy conflict.
-
B.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
C.
opponentMonarch
Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
-
D.
opponentInScenario
chosen
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
E.
opponentTitle
Indicates that the object is the formal title or designation held by an opponent in a competitive or adversarial context.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3ba9aca48190b5180eefd61a9fdc |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.