Triple
T29889934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Nights: The Album |
E759121
|
entity |
| Predicate | hasPredecessorWork |
P59481
|
FINISHED |
| Object | Late Nights with Jeremih |
—
|
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: Late Nights with Jeremih | Statement: [Late Nights: The Album, hasPredecessorWork, Late Nights with Jeremih]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorWork Context triple: [Late Nights: The Album, hasPredecessorWork, Late Nights with Jeremih]
-
A.
hasPrecedingWork
chosen
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
B.
hasPredecessorMission
Indicates that a mission occurs after and is directly preceded by another specific mission in a sequence.
-
C.
hasPredecessorMP
Indicates that one member of parliament previously held the same parliamentary position or seat before another member of parliament.
-
D.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
E.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 29, 2026, 6:02 p.m.