Triple
T15571338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan, Texas |
E374248
|
entity |
| Predicate | primaryEthnicCulture |
P44820
|
FINISHED |
| Object | Mexican American |
—
|
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: Mexican American | Statement: [San Juan, Texas, primaryEthnicCulture, Mexican American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEthnicCulture Context triple: [San Juan, Texas, primaryEthnicCulture, Mexican American]
-
A.
primaryEthnicFocus
Indicates that something is chiefly oriented toward, concerned with, or designed for a particular ethnic group as its main focus.
-
B.
primaryCulture
chosen
Indicates the main or dominant culture associated with an entity, typically in contrast to any secondary or additional cultures.
-
C.
dominantCulture
Indicates that one culture holds prevailing power, influence, or normative status over others within a given social context.
-
D.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
E.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2025888190a2b6240296bba13e |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.