Triple
T15083926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul City, North Carolina |
E360220
|
entity |
| Predicate | intendedDemographic |
P10804
|
FINISHED |
| Object | majority Black population |
—
|
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: majority Black population | Statement: [Soul City, North Carolina, intendedDemographic, majority Black population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedDemographic Context triple: [Soul City, North Carolina, intendedDemographic, majority Black population]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
C.
involvesDemographic
Indicates that an action, event, or entity is related to, affects, or includes a specific demographic group or population segment.
-
D.
intendedForAgeGroup
Indicates that something is designed, suitable, or targeted for use by a specific age group.
-
E.
targetedPopulation
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
- 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.