Triple

T3186608
Position Surface form Disambiguated ID Type / Status
Subject CSRA economic region E66712 entity
Predicate hasPlanningFunction P46513 FINISHED
Object coordination of economic policy across counties 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: coordination of economic policy across counties | Statement: [CSRA economic region, hasPlanningFunction, coordination of economic policy across counties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlanningFunction
Context triple: [CSRA economic region, hasPlanningFunction, coordination of economic policy across counties]
  • A. hasPlanningLevel
    Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
  • B. hasPlanningCharacteristic
    Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
  • C. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • D. hasPlanningStyle
    Indicates that an entity is associated with or characterized by a particular style or approach to planning.
  • E. hasPlan
    Indicates that an entity possesses or is associated with a specific plan or course of action.
  • 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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6c32ce88190a231be18d38ec5ba completed March 8, 2026, 4:41 p.m.
PD Predicate disambiguation batch_69ad9e04290481909092ddfbe6fdaabc completed March 8, 2026, 4:04 p.m.
PDg Predicate description generation batch_69ada148e9108190b363dd0f1a94ac8e completed March 8, 2026, 4:18 p.m.
Created at: March 8, 2026, 3:06 p.m.