Triple

T32705247
Position Surface form Disambiguated ID Type / Status
Subject Tahara E836255 entity
Predicate offersFerryRouteTo P1737 FINISHED
Object Toba 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: Toba | Statement: [Tahara, offersFerryRouteTo, Toba]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offersFerryRouteTo
Context triple: [Tahara, offersFerryRouteTo, Toba]
  • A. hasFerryService chosen
    Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
  • B. hasNearbyFerryRoute
    Indicates that there is a ferry route located close to the referenced entity.
  • C. isOneOfMainCarFerryRoutesTo
    Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
  • D. hasFerryType
    Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
  • E. hasFerryComponent
    Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
  • 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_69f3493446148190819541f3ffe79975 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd7e364a648190a1e9e1d9fc76e99e completed May 8, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69fd7bb547608190a3b04dddbca6b8bc completed May 8, 2026, 5:59 a.m.
Created at: May 1, 2026, 1:10 a.m.