Triple
T38303559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ὠκεανός |
E1032284
|
entity |
| Predicate | participationInTitanomachy |
P25411
|
FINISHED |
| Object | remained neutral |
—
|
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: remained neutral | Statement: [Ὠκεανός, participationInTitanomachy, remained neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationInTitanomachy Context triple: [Ὠκεανός, participationInTitanomachy, remained neutral]
-
A.
sideTakenInTitanomachy
chosen
Indicates which faction or side an entity aligned with or supported during the Titanomachy conflict.
-
B.
takesSideInTrojanWar
Indicates that an entity participates in the Trojan War as a supporter of one of the opposing sides.
-
C.
roleInTrojanWar
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
-
D.
helpedZeusWith
Indicates that one entity provided assistance or support to Zeus in accomplishing a task or dealing with a situation.
-
E.
goalInTrojanWar
Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:30 p.m.