Triple

T11350971
Position Surface form Disambiguated ID Type / Status
Subject Vulcano Porto E268837 entity
Predicate connectsByFerryTo P1831 FINISHED
Object Salina E268840 NE 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: Salina | Statement: [Vulcano Porto, connectsByFerryTo, Salina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salina
Context triple: [Vulcano Porto, connectsByFerryTo, Salina]
  • A. Salina chosen
    Salina is a volcanic island in Italy's Aeolian archipelago, known for its lush landscapes, twin extinct volcanoes, and production of Malvasia wine.
  • B. Eudora
    Eudora is a figure from Greek mythology known as one of the daughters of the Titan Atlas.
  • C. Salina micropolitan area
    The Salina micropolitan area is a small urban region in central Kansas centered around the city of Salina and its surrounding communities.
  • D. Seneca, Kansas
    Seneca, Kansas is a small city in northeastern Kansas that serves as a local commercial and community hub for the surrounding rural region.
  • E. Larimore
    Larimore is a small city in eastern North Dakota, United States, known for its rural character and proximity to Grand Forks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aacbe18081909e5fadb50082dd96 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea23391c819089e8f9725cb3a0ff completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e58b8d5f5c8190a80a52f2063bb5b0 completed April 20, 2026, 2:12 a.m.
Created at: April 8, 2026, 9:33 p.m.