Triple

T34664803
Position Surface form Disambiguated ID Type / Status
Subject Fregon E890221 entity
Predicate hasOutstationLinks P113639 FINISHED
Object nearby homelands and outstations 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: nearby homelands and outstations | Statement: [Fregon, hasOutstationLinks, nearby homelands and outstations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOutstationLinks
Context triple: [Fregon, hasOutstationLinks, nearby homelands and outstations]
  • A. hasOutstations chosen
    Indicates that an entity maintains or is associated with one or more subsidiary locations or branches situated away from its main base or headquarters.
  • B. hasCommuterLinks
    Indicates that there are established transportation connections enabling regular travel between two locations.
  • C. hasInterchangeStationWith
    Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
  • D. hasLandsideConnection
    Indicates that two locations are connected by a route or access on land, allowing movement between them without using air or water transport.
  • E. hasMajorRailLinksTo
    Indicates that there are significant railway connections or routes between two locations.
  • 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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f73397e5488190a9cdce98a0ac0383 completed May 3, 2026, 11:38 a.m.
PD Predicate disambiguation batch_69f732f3ad248190b4bcbf589d000f0d completed May 3, 2026, 11:35 a.m.
Created at: May 1, 2026, 2:04 a.m.