Triple

T17469179
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 226 E425358 entity
Predicate traversesMunicipality P15633 FINISHED
Object Randolph, Maine 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: Randolph, Maine | Statement: [Maine State Route 226, traversesMunicipality, Randolph, Maine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traversesMunicipality
Context triple: [Maine State Route 226, traversesMunicipality, Randolph, Maine]
  • A. isInMunicipality
    Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
  • B. spansMunicipality chosen
    Indicates that something (such as an area, structure, or feature) extends across or covers more than one municipality.
  • C. mainMunicipality
    Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
  • D. isMunicipalHomeOf
    Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
  • E. municipality
    Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451aad4a08190be7e25841da8e952 completed April 19, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69e3b4f341c88190adabe526d8903b05 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.