Triple

T28986773
Position Surface form Disambiguated ID Type / Status
Subject Boundary Road E734706 entity
Predicate isBoundary P71578 FINISHED
Object municipal boundary line 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: municipal boundary line | Statement: [Boundary Road, isBoundary, municipal boundary line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBoundary
Context triple: [Boundary Road, isBoundary, municipal boundary line]
  • A. isBoundaryFor chosen
    Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
  • B. isLegalBoundary
    Indicates that something serves as an officially recognized dividing line that defines the limits of a legal jurisdiction, property, or authority.
  • C. hasBoundaryCriterion
    Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
  • D. hasBoundaryType
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • E. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • 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_69f05b0dd9b481908b7901e1c95ff6b2 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65f7994088190bab22373bcce6847 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f659d02f1c8190831758ac52bb54e4 completed May 2, 2026, 8:08 p.m.
Created at: April 28, 2026, 9:15 a.m.