Triple
T24835469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulaski Square |
E621457
|
entity |
| Predicate | cityPlanElement |
P68711
|
FINISHED |
| Object | Oglethorpe Plan |
—
|
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: Oglethorpe Plan | Statement: [Pulaski Square, cityPlanElement, Oglethorpe Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityPlanElement Context triple: [Pulaski Square, cityPlanElement, Oglethorpe Plan]
-
A.
urbanDesignElement
Indicates a relationship where something functions as a designed feature or component that shapes the form, use, or experience of an urban environment.
-
B.
urbanPlanBy
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
-
C.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
D.
partOfCityPlan
chosen
Indicates that something is included as a component or element within a broader city planning scheme or framework.
-
E.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:17 a.m.