Triple
T14825486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radburn, New Jersey |
E348559
|
entity |
| Predicate | followsPlanningConcept |
P56805
|
FINISHED |
| Object | garden city movement |
—
|
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: garden city movement | Statement: [Radburn, New Jersey, followsPlanningConcept, garden city movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPlanningConcept Context triple: [Radburn, New Jersey, followsPlanningConcept, garden city movement]
-
A.
hasPlanningConcept
chosen
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
B.
followsInConcept
Indicates that one concept comes after or is derived from another concept in a logical, thematic, or conceptual sequence.
-
C.
followsPlanType
Indicates that one entity adheres to, or is carried out according to, a specified type of plan.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0713700819097bbb0352650984b |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.