Triple
T30595883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Please Don’t Stop Loving Me |
E778786
|
entity |
| Predicate | hasCollaborationPeriod |
P65841
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Please Don’t Stop Loving Me, hasCollaborationPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborationPeriod Context triple: [Please Don’t Stop Loving Me, hasCollaborationPeriod, 1970s]
-
A.
collaborationPeriod
chosen
Indicates the time span during which two or more entities are actively engaged in a collaborative relationship or joint activity.
-
B.
collaborationPeriodWith
Indicates the time span during which two or more entities are engaged in a collaborative relationship or joint activity.
-
C.
hasSubsequentCollaboration
Indicates that one entity engages in a follow-up or later collaboration with another entity after an initial joint activity or partnership.
-
D.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
E.
hasPeriodOf
Indicates that one entity possesses, experiences, or is associated with a specific span or interval of time.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
Created at: April 29, 2026, 8:24 p.m.