Triple

T7817055
Position Surface form Disambiguated ID Type / Status
Subject Eixo Rodoviário E181035 entity
Predicate positionInPlan P79168 FINISHED
Object one of the main structural axes of Brasília’s pilot plan 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: one of the main structural axes of Brasília’s pilot plan | Statement: [Eixo Rodoviário, positionInPlan, one of the main structural axes of Brasília’s pilot plan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionInPlan
Context triple: [Eixo Rodoviário, positionInPlan, one of the main structural axes of Brasília’s pilot plan]
  • A. positionOn
    Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
  • B. positionInCase
    Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
  • C. positionInState
    Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
  • D. plannedLocation
    Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
  • E. positionB
    Indicates that one entity occupies or is located at a specific position relative to 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_69ca828153f48190bdb27ac46f8e0745 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69caf96ea6d881908eff5f750e0f6700 completed March 30, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69cae91687788190af9cb7aaa996d291 completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf7855a3c81908b9318f7186fc0c0 completed March 30, 2026, 10:21 p.m.
Created at: March 30, 2026, 4:39 p.m.