Triple
T23547112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Down |
E577928
|
entity |
| Predicate | hasChronologyPreviousWork |
P59481
|
FINISHED |
| Object | earlier Swizz Beatz singles |
—
|
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: earlier Swizz Beatz singles | Statement: [Top Down, hasChronologyPreviousWork, earlier Swizz Beatz singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChronologyPreviousWork Context triple: [Top Down, hasChronologyPreviousWork, earlier Swizz Beatz singles]
-
A.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
B.
chronologyPreviousWorkOf
Indicates that one work temporally precedes and is part of the earlier sequence in the overall body of another work.
-
C.
previousWorkAfterHiatusOf
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
D.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
E.
hasPrecedingWork
chosen
Indicates that one work comes before another in a sequence, serving as its predecessor.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.