Triple

T26239532
Position Surface form Disambiguated ID Type / Status
Subject Schouten Islands E656271 entity
Predicate hasTransportHubOn P2413 FINISHED
Object Biak E1336573 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: Biak | Statement: [Schouten Islands, hasTransportHubOn, Biak]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportHubOn
Context triple: [Schouten Islands, hasTransportHubOn, Biak]
  • A. hasTransportHub chosen
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • B. isGroundTransportHubFor
    Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
  • C. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • D. isKeyTransportHubIn
    Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
  • E. isTransportHubBetween
    Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
  • F. None of above.

Provenance (4 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_69ee5b4c59a881909d9ee4fd013fffd5 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11bb001b948190a969e6d8820b3708 completed May 23, 2026, 2:34 p.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: April 26, 2026, 9:03 p.m.