Triple
T4786463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobbham Historic District |
E106489
|
entity |
| Predicate | hasPlanningPattern |
P58411
|
FINISHED |
| Object | grid street pattern |
—
|
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: grid street pattern | Statement: [Cobbham Historic District, hasPlanningPattern, grid street pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningPattern Context triple: [Cobbham Historic District, hasPlanningPattern, grid street pattern]
-
A.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
B.
hasPlanningStyle
Indicates that an entity is associated with or characterized by a particular style or approach to planning.
-
C.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
D.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
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. 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65d8f9d881909c24340b8dc6a104 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.