Triple
T29508057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Rompe Corazones |
E748568
|
entity |
| Predicate | hasMainVocalLanguage |
P118705
|
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: [La Rompe Corazones, hasMainVocalLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainVocalLanguage Context triple: [La Rompe Corazones, hasMainVocalLanguage, Spanish]
-
A.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
B.
primaryVocalLanguage
chosen
Indicates the main spoken language typically used by an entity for vocal communication.
-
C.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
-
D.
isSpokenAsFirstLanguageBy
Indicates that a language is the primary (native) language used by a person or group for everyday communication.
-
E.
isSpokenLanguageOf
Indicates that a particular language is used as the spoken language by a specified person, group, or community.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 28, 2026, 4:29 p.m.