Triple
T4736917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaeacians |
E105146
|
entity |
| Predicate | opposedByDeity |
P437
|
FINISHED |
| Object | Poseidon after they help Odysseus |
—
|
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: Poseidon after they help Odysseus | Statement: [Phaeacians, opposedByDeity, Poseidon after they help Odysseus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedByDeity Context triple: [Phaeacians, opposedByDeity, Poseidon after they help Odysseus]
-
A.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
B.
involvesDeity
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
C.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.