Triple
T32696733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Parade, Bath |
E836028
|
entity |
| Predicate | isPartOfPlanningBy |
P14107
|
FINISHED |
| Object | John Wood the Elder |
—
|
NE NERFINISHED |
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: John Wood the Elder | Statement: [South Parade, Bath, isPartOfPlanningBy, John Wood the Elder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPlanningBy Context triple: [South Parade, Bath, isPartOfPlanningBy, John Wood the Elder]
-
A.
partOfUrbanPlanBy
chosen
Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
-
B.
isPartOfTransportPlan
Indicates that something is included as a component or element within a broader transport plan.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 1:10 a.m.