Triple
T31287472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let's Work |
E797840
|
entity |
| Predicate | hasPreviousSingle |
P91828
|
FINISHED |
| Object | Lucky in Love |
—
|
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: Lucky in Love | Statement: [Let's Work, hasPreviousSingle, Lucky in Love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviousSingle Context triple: [Let's Work, hasPreviousSingle, Lucky in Love]
-
A.
hasPreviousFunction
Indicates that an entity was assigned a different function or role at an earlier time.
-
B.
isPrecededBySingle
chosen
Indicates that one entity occurs immediately before another entity, with exactly one direct predecessor in the sequence.
-
C.
hasPreviousProduct
Indicates that an entity is linked to another entity that came immediately before it in a sequence of products.
-
D.
hasPreviousHolder
Indicates that an entity was formerly held, occupied, or possessed by another specified entity before the current one.
-
E.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: April 29, 2026, 9:14 p.m.