Triple

T20133928
Position Surface form Disambiguated ID Type / Status
Subject Lake Lerna E490969 entity
Predicate hydraDescription P138809 FINISHED
Object multi-headed serpent-like monster 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: multi-headed serpent-like monster | Statement: [Lake Lerna, hydraDescription, multi-headed serpent-like monster]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hydraDescription
Context triple: [Lake Lerna, hydraDescription, multi-headed serpent-like monster]
  • A. hasHyphae
    Indicates that an organism possesses hyphae, the filamentous structures characteristic of fungi.
  • B. harbor
    Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
  • C. hasHydrosphere
    Indicates that an entity possesses or is characterized by a surrounding layer or system of water, such as oceans, seas, lakes, or other bodies of liquid water.
  • D. HethIs
    Indicates that one entity is identified as or equated with another entity, expressing a basic “is” or “being” relationship between them.
  • E. harborDescription
    Indicates that one entity serves as a harbor or safe anchorage location for another entity, typically providing shelter, docking, or protection.
  • 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6676556c481909ffc80cd2009b65a completed April 20, 2026, 5:50 p.m.
PD Predicate disambiguation batch_69e54cfb0d0081908e789b9b57e96668 completed April 19, 2026, 9:45 p.m.
PDg Predicate description generation batch_69e54fc2bc3c819088c33cd263303433 completed April 19, 2026, 9:57 p.m.
Created at: April 11, 2026, 11:32 p.m.