Triple
T34336942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadie Quiere Estar Solo |
E881172
|
entity |
| Predicate | sharesArrangementWith |
P201541
|
FINISHED |
| Object | Nobody Wants to Be Lonely |
—
|
NE NERFINISHED |
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: Nobody Wants to Be Lonely | Statement: [Nadie Quiere Estar Solo, sharesArrangementWith, Nobody Wants to Be Lonely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesArrangementWith Context triple: [Nadie Quiere Estar Solo, sharesArrangementWith, Nobody Wants to Be Lonely]
-
A.
sharesRuleWith
Indicates that two or more entities are governed by, comply with, or are associated with the same rule or set of rules.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
E.
sharesRevenueWith
Indicates that one entity distributes a portion of its revenue to another entity as part of a revenue-sharing arrangement.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
| PDg | Predicate description generation | batch_6a00037aff7c8190940bd1b02cec8c57 |
completed | May 10, 2026, 4:03 a.m. |
Created at: May 1, 2026, 1:58 a.m.