Triple
T1698994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Towns Act 1946 |
E36724
|
entity |
| Predicate | typeOfPlanning |
P8653
|
FINISHED |
| Object | state-led planned development |
—
|
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: state-led planned development | Statement: [New Towns Act 1946, typeOfPlanning, state-led planned development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPlanning Context triple: [New Towns Act 1946, typeOfPlanning, state-led planned development]
-
A.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
B.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
C.
planningNation
Indicates that a nation is responsible for planning, organizing, or coordinating the referenced activity, event, or operation.
-
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.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.