Triple
T6380463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oye Como Va |
E143565
|
entity |
| Predicate | hasMeaningOfTitle |
P4542
|
FINISHED |
| Object | “Listen to how it goes” in English |
—
|
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: “Listen to how it goes” in English | Statement: [Oye Como Va, hasMeaningOfTitle, “Listen to how it goes” in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningOfTitle Context triple: [Oye Como Va, hasMeaningOfTitle, “Listen to how it goes” in English]
-
A.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasTitlePun
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
E.
hasMeaningViaJohn
Indicates that something possesses or conveys its meaning specifically through John as the interpretive or mediating agent.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0685265208190b2204bd4abff2668 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.