Triple

T12548195
Position Surface form Disambiguated ID Type / Status
Subject Fujiko F. Fujio Museum E300026 entity
Predicate hasShuttleBus P3493 FINISHED
Object service from Noborito Station 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: service from Noborito Station | Statement: [Fujiko F. Fujio Museum, hasShuttleBus, service from Noborito Station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasShuttleBus
Context triple: [Fujiko F. Fujio Museum, hasShuttleBus, service from Noborito Station]
  • A. hasShuttleLine chosen
    Indicates that there is a shuttle service or route operating between the related entities.
  • B. hasBusServices
    Indicates that one location or entity is served by bus routes or bus transportation provided by another.
  • C. hasFormOfPublicTransit
    Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
  • D. hasPublicTransitRoute
    Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
  • E. hasPublicTransitFunction
    Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d95410d0b0819097646edd1b837104 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 9:58 p.m.