Triple
T5029540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuyo |
E113261
|
entity |
| Predicate | originalNetworkUsage |
P60613
|
FINISHED |
| Object | Narcos opening theme |
—
|
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: Narcos opening theme | Statement: [Tuyo, originalNetworkUsage, Narcos opening theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkUsage Context triple: [Tuyo, originalNetworkUsage, Narcos opening theme]
-
A.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
-
B.
originalNetworkName
Indicates the name of the network from which something (e.g., data, content, or a connection) originally came.
-
C.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
-
D.
dnsUsage
Indicates that one entity uses or relies on another entity for Domain Name System (DNS) resolution or related DNS services.
-
E.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd739099a0819099c6201d4e1c5ee2 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.