Triple
T28139673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanglish |
E714310
|
entity |
| Predicate | usesCodeSwitchingBetween |
P85150
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Spanglish, usesCodeSwitchingBetween, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodeSwitchingBetween Context triple: [Spanglish, usesCodeSwitchingBetween, Spanish]
-
A.
codeSwitchedTo
chosen
Indicates that an entity has changed from using one language or code system to another within a given context or interaction.
-
B.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
C.
usedAsContactLanguageBetween
Indicates that a language functions as the medium of communication between two or more distinct language communities.
-
D.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
E.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 9:52 p.m.