Triple

T2718899
Position Surface form Disambiguated ID Type / Status
Subject International Planning Associates E60032 entity
Predicate planningScope P25607 FINISHED
Object city-scale master planning 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: city-scale master planning | Statement: [International Planning Associates, planningScope, city-scale master planning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: planningScope
Context triple: [International Planning Associates, planningScope, city-scale master planning]
  • A. plannedUnder
    Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
  • B. missionScope
    Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
  • C. hasPlanningLevel
    Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
  • D. planningDocument
    Indicates that an entity serves as or is associated with a document created for planning or outlining future actions, strategies, or activities.
  • E. scopeType chosen
    Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
  • 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_69ab4b746d248190958e052045c09255 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdaaee104819085966bc54d5da9c0 completed March 7, 2026, 7:58 a.m.
PD Predicate disambiguation batch_69abd8240920819087a812d816a55edb completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.