Triple
T32350803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Before the Next Teardrop Falls |
E826588
|
entity |
| Predicate | featuresLanguageSwitch |
P4292
|
FINISHED |
| Object | English to 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: English to Spanish | Statement: [Before the Next Teardrop Falls, featuresLanguageSwitch, English to Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLanguageSwitch Context triple: [Before the Next Teardrop Falls, featuresLanguageSwitch, English to Spanish]
-
A.
navigationLanguage
Indicates the language used for navigation-related content, such as menus, directions, or interface controls.
-
B.
languageShift
chosen
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
C.
languageVariants
Indicates that one language form is a variant or alternative version of another language.
-
D.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
-
E.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 1, 2026, 12:49 a.m.