Triple

T588697
Position Surface form Disambiguated ID Type / Status
Subject Pioneer Courthouse E17218 entity
Predicate locatedOnSquare P40 FINISHED
Object Pioneer Courthouse Square vicinity 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: Pioneer Courthouse Square vicinity | Statement: [Pioneer Courthouse, locatedOnSquare, Pioneer Courthouse Square vicinity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedOnSquare
Context triple: [Pioneer Courthouse, locatedOnSquare, Pioneer Courthouse Square vicinity]
  • A. locatedIn chosen
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • B. locatedAlong
    Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
  • C. hasNearbySquare
    Indicates that one entity has at least one square-shaped entity located close to it in space.
  • D. locatedAtInteractionPoint
    Indicates that an entity is positioned at a specific interaction point where interactions or exchanges are intended to occur.
  • E. locatedAtIntersectionOf
    Indicates that something is situated at the point where two or more paths, roads, or boundaries cross or meet.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b9d1e68819096a9b5e7b2e83d6e completed March 1, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69a494ca68448190a516b9c3525d8916 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.