Triple
T19197007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis, Colorado |
E469996
|
entity |
| Predicate | demographicHeritage |
P194
|
FINISHED |
| Object | Hispano community |
—
|
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: Hispano community | Statement: [San Luis, Colorado, demographicHeritage, Hispano community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicHeritage Context triple: [San Luis, Colorado, demographicHeritage, Hispano community]
-
A.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
-
B.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
demographicCharacteristic
Indicates that one entity specifies or describes a demographic attribute or feature (such as age, gender, ethnicity, or similar population-related trait) of another entity.
-
D.
ethnicComponents
Indicates that an entity is composed of, associated with, or characterized by one or more specified ethnic groups or ethnic origins.
-
E.
demographicsDescriptor
Indicates a descriptive attribute or classification that characterizes the demographic properties of an entity or group.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a695cc8190b84a220f52c51dfc |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.