Triple

T1219920
Position Surface form Disambiguated ID Type / Status
Subject Oceanus E26195 entity
Predicate poseidonRelation P25958 FINISHED
Object distinct from the Olympian sea god Poseidon 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: distinct from the Olympian sea god Poseidon | Statement: [Oceanus, poseidonRelation, distinct from the Olympian sea god Poseidon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: poseidonRelation
Context triple: [Oceanus, poseidonRelation, distinct from the Olympian sea god Poseidon]
  • A. relatedNameOfGod
    Indicates that one entity is a name, title, or designation that refers to or is associated with God.
  • B. datumRelation
    Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
  • C. linkedToMythology
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • D. pantheon
    Indicates a relationship where a group of deities collectively belong to or are recognized within the same religious or mythological system.
  • E. definesRelationshipBetween
    Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
  • F. None of above. chosen

Provenance (4 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be1ead088190bf44dc6ab1edf18b completed March 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69a4bb644af08190ba25905f20adb01a completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bd3140688190ac6e24de157fd61e completed March 1, 2026, 10:26 p.m.
Created at: March 1, 2026, 7:46 p.m.