Triple

T35918860
Position Surface form Disambiguated ID Type / Status
Subject Behabad E1038824 entity
Predicate localEconomicRole P2223 FINISHED
Object local economic center 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: local economic center | Statement: [Behabad, localEconomicRole, local economic center]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localEconomicRole
Context triple: [Behabad, localEconomicRole, local economic center]
  • A. partOfLocalEconomy
    Indicates that an entity contributes to, participates in, or is integrated within the economic activities of a specific local area or community.
  • B. localEconomyImpact
    Indicates the effect that an action, event, or entity has on the economic conditions, activities, or performance of a specific local area or community.
  • C. socioeconomicRole
    Indicates the social and economic position, function, or status an entity holds within a society or system.
  • D. hasEconomicRole chosen
    Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
  • E. urbanRole
    Indicates the function, status, or role that an entity holds within an urban or city context.
  • 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_69f76e2320748190b7f5c4750d0cd0d3 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7c29e1b848190b945c6c6120a5330 completed May 3, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f7c1b6e7a881908deb96bedb2713f4 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:07 p.m.