Triple

T38485694
Position Surface form Disambiguated ID Type / Status
Subject Mile Road System (Detroit) E917908 entity
Predicate coordinateSystemFor P191634 FINISHED
Object suburban development patterns 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: suburban development patterns | Statement: [Mile Road System (Detroit), coordinateSystemFor, suburban development patterns]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinateSystemFor
Context triple: [Mile Road System (Detroit), coordinateSystemFor, suburban development patterns]
  • A. coordinateSystem
    Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
  • B. coordinateSystemBehavior
    Indicates how positions, orientations, or transformations are defined, interpreted, and updated within a particular coordinate system.
  • C. coordinateSystemStorage
    Indicates how a coordinate system is stored, encoded, or represented within a given context or system.
  • D. coordinateSystemObserved
    Indicates that one entity is observed, measured, or expressed within the reference frame or coordinate system defined by another entity.
  • E. coordinateOf
    Indicates that one entity specifies the spatial or positional coordinates associated with another entity.
  • F. None of above. chosen

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_69f76e9894208190a129a553a60ca58c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fce28d6c3081908bf76f5db63ecf68 completed May 7, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69fce12d2f08819082134b5eb3db6a24 completed May 7, 2026, 6:59 p.m.
PDg Predicate description generation batch_69fce28a74508190aab36551094e8226 completed May 7, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:31 p.m.