Triple
T20296147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everything I Have Is Yours |
E505355
|
entity |
| Predicate | isRomanticStandard |
P121824
|
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: [Everything I Have Is Yours, isRomanticStandard, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRomanticStandard Context triple: [Everything I Have Is Yours, isRomanticStandard, true]
-
A.
isRomanticPopStandard
chosen
Indicates that a song is recognized as a widely known, enduring standard within the romantic pop music genre.
-
B.
isCulturalStandardFor
Indicates that something is recognized or accepted as the customary or normative practice, value, or behavior within a particular culture or cultural context.
-
C.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
D.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67707f770819093742d7509fe9bdd |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:15 a.m.