Triple

T30674033
Position Surface form Disambiguated ID Type / Status
Subject King of Atlantis E780864 entity
Predicate conflictsInvolvingTitle P5022 FINISHED
Object surface world vs Atlantis tensions 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: surface world vs Atlantis tensions | Statement: [King of Atlantis, conflictsInvolvingTitle, surface world vs Atlantis tensions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conflictsInvolvingTitle
Context triple: [King of Atlantis, conflictsInvolvingTitle, surface world vs Atlantis tensions]
  • A. conflictsInvolvedIn
    Indicates that an entity participates as a party or actor in one or more conflicts.
  • B. involvesTitle
    Indicates that the relationship or action includes or makes reference to a specific title (such as a role, honorific, or formal designation).
  • C. notableConflictWith
    Indicates a significant, recognized conflict or dispute that exists or has existed between the related entities.
  • D. titleContestedIn
    Indicates that a particular title or championship is being challenged or competed for within a specific event, match, or context.
  • E. mainConflict chosen
    Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
  • 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_69f224a7fc208190a07d6d3879b31640 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a7bdb481908d16a32f49e38c2c completed May 3, 2026, 2:32 a.m.
Created at: April 29, 2026, 8:32 p.m.