Triple

T24347696
Position Surface form Disambiguated ID Type / Status
Subject Mokpo E613689 entity
Predicate hasFerryRoutesTo P1737 FINISHED
Object Heuksando NE NERFINISHED

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: Heuksando | Statement: [Mokpo, hasFerryRoutesTo, Heuksando]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFerryRoutesTo
Context triple: [Mokpo, hasFerryRoutesTo, Heuksando]
  • A. hasFerryService chosen
    Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
  • B. hasFerryPort
    Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
  • C. hasFerryComponent
    Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
  • D. hasFerryType
    Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
  • E. hasNearbyFerryRoute
    Indicates that there is a ferry route located close to the referenced entity.
  • 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_69e2d7ddd29481909e7f539a6072bd71 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2932a49b081908b63b1354dfa6583 completed April 29, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69f287ad30048190b3ad3613486f277f completed April 29, 2026, 10:35 p.m.
Created at: April 18, 2026, 1:58 a.m.