Triple

T544744
Position Surface form Disambiguated ID Type / Status
Subject Glenrothes Development Corporation E12706 entity
Predicate usesPlanningInstrument P933 FINISHED
Object 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: master planning | Statement: [Glenrothes Development Corporation, usesPlanningInstrument, master planning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesPlanningInstrument
Context triple: [Glenrothes Development Corporation, usesPlanningInstrument, master planning]
  • A. plannedUseOf
    Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
  • B. plannedUnder
    Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
  • C. usesInstrument chosen
    Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
  • D. partOfUrbanPlanBy
    Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
  • E. hasPlannedInstitution
    Indicates that an entity has an associated institution that is intended or scheduled to be established or implemented in the future.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a498dfec5c81908b76d723b30dc2f0 completed March 1, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69a494b8098481908097228db8ad0262 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.