Triple
T3240629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish new towns programme |
E67956
|
entity |
| Predicate | planningModel |
P33328
|
FINISHED |
| Object | comprehensive 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: comprehensive master planning | Statement: [Scottish new towns programme, planningModel, comprehensive master planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningModel Context triple: [Scottish new towns programme, planningModel, comprehensive master planning]
-
A.
planningModelFor
chosen
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to 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.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
D.
planningStarted
Indicates that the process of planning for a particular task, project, or event has been initiated.
-
E.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef6430081909084589f6eea5c7e |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.