Triple

T11109384
Position Surface form Disambiguated ID Type / Status
Subject Daanbantayan E262714 entity
Predicate hasPort P35 FINISHED
Object Maya Port E562615 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: Maya Port | Statement: [Daanbantayan, hasPort, Maya Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maya Port
Context triple: [Daanbantayan, hasPort, Maya Port]
  • A. Maya Port chosen
    Maya Port is a small ferry terminal in northern Cebu, Philippines, serving as the main jump-off point for boats traveling to Malapascua Island.
  • B. Naha Port
    Naha Port is a major seaport in Naha, Okinawa, serving as a key hub for passenger ferries, cargo shipping, and cruise ships in Japan’s Ryukyu Islands.
  • C. Kada Port
    Kada Port is a coastal harbor in Wakayama, Japan, serving as the main departure point for ferries to the nearby Tomogashima Islands.
  • D. Velas
    Velas is a coastal town and municipality on São Jorge Island in Portugal’s Azores archipelago, known for its dramatic cliffs, natural pools, and traditional Azorean architecture.
  • E. Mwanza Port
    Mwanza Port is a major Tanzanian inland port on Lake Victoria that serves as a key hub for regional transport and trade in the Mwanza area.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79a6896c0819082685b5b4600d158 completed April 9, 2026, 12:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69e42d72f8f48190a7414119a6be9d5e completed April 19, 2026, 1:18 a.m.
Created at: April 8, 2026, 9:27 p.m.