Triple
T34135847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telepatía |
E875563
|
entity |
| Predicate | hasBilingualLyrics |
P181474
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Telepatía, hasBilingualLyrics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBilingualLyrics Context triple: [Telepatía, hasBilingualLyrics, true]
-
A.
hasLyricalLanguage
Indicates that something (such as a text or expression) employs poetic, expressive, or highly figurative language.
-
B.
hasAdditionalLyrics
Indicates that an entity (such as a song or track) includes extra or supplementary lyrics beyond a primary or original set.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
isOnBilingualThemedAlbum
Indicates that an item (such as a song or track) appears on an album whose theme or content prominently involves two languages.
-
E.
hasAdditionalLyricsBy
Indicates that an entity (such as a musical work or track) includes extra or modified lyrics contributed by a specified person or group beyond the original lyricist.
- F. None of above. chosen
Provenance (4 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 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. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: May 1, 2026, 1:53 a.m.