Triple
T15083920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul City, North Carolina |
E360220
|
entity |
| Predicate | majorPlanningPeriod |
P97000
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Soul City, North Carolina, majorPlanningPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPlanningPeriod Context triple: [Soul City, North Carolina, majorPlanningPeriod, 1970s]
-
A.
urbanPlanningPeriod
chosen
Indicates the specific span of time during which urban planning activities, policies, or projects are designed, implemented, or in effect.
-
B.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
C.
zoningPlanPeriod
Indicates the time span or duration for which a particular zoning plan is valid or in effect.
-
D.
majorRedevelopmentPeriod
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
E.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00275cfa88190a13fe20b585d9fcb |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.