Triple
T23566734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Only Want to Be with You |
E579390
|
entity |
| Predicate | hasKeyReissueDecade |
P153185
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [I Only Want to Be with You, hasKeyReissueDecade, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyReissueDecade Context triple: [I Only Want to Be with You, hasKeyReissueDecade, 1990s]
-
A.
hasKeyReissue
Indicates that a key has been issued again to an entity, typically replacing or updating a previous key.
-
B.
hasReissuePeriod
Indicates the time span during which something (such as a document, license, or product) may be reissued or renewed.
-
C.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
-
D.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
E.
hasKeyIssue
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6d3dcc8190bb127632e101a053 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:35 p.m.