Triple
T16912147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peachtree Corners, Georgia |
E410225
|
entity |
| Predicate | developmentOrigin |
P75699
|
FINISHED |
| Object | planned suburban 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: planned suburban development | Statement: [Peachtree Corners, Georgia, developmentOrigin, planned suburban development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentOrigin Context triple: [Peachtree Corners, Georgia, developmentOrigin, planned suburban development]
-
A.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
B.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
-
D.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
E.
originallyDevelopedIn
chosen
Indicates that something (such as a product, technology, or idea) was first created, designed, or developed in a particular place or context.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3d6be88190bca5e1fdf727141b |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.