Triple
T8428519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loca |
E199060
|
entity |
| Predicate | vocalLanguageOfWork |
P47965
|
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: [Loca, vocalLanguageOfWork, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalLanguageOfWork Context triple: [Loca, vocalLanguageOfWork, Spanish]
-
A.
languageOfVocalization
chosen
Indicates the language in which a vocalization (such as speech or singing) is produced.
-
B.
languageOfParentWork
Indicates that the specified language is the language in which the parent (original or containing) work is expressed.
-
C.
performedLanguage
Indicates that an action, work, or performance was carried out using a specified language.
-
D.
originalLanguageOfWholeWork
Indicates that a given language is the primary or original language in which an entire work (such as a book, film, or other complete creation) was first produced or expressed.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.