Triple
T28139710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanglish |
E714310
|
entity |
| Predicate | hasCulturalDebate |
P142728
|
FINISHED |
| Object | language purity concerns |
—
|
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: language purity concerns | Statement: [Spanglish, hasCulturalDebate, language purity concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalDebate Context triple: [Spanglish, hasCulturalDebate, language purity concerns]
-
A.
hasSubcultureDebate
Indicates that there is an ongoing or notable debate, disagreement, or contested discourse within or about a particular subculture.
-
B.
hasDebateAround
chosen
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
C.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
D.
debatedBetween
Indicates a situation in which two or more parties engage in a discussion or argument over differing views about a particular issue or topic.
-
E.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 9:52 p.m.