Triple
T21845090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell on Earth |
E539352
|
entity |
| Predicate | chronologicallyInSeries |
P94975
|
FINISHED |
| Object | third Mobb Deep studio album |
—
|
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: third Mobb Deep studio album | Statement: [Hell on Earth, chronologicallyInSeries, third Mobb Deep studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyInSeries Context triple: [Hell on Earth, chronologicallyInSeries, third Mobb Deep studio album]
-
A.
chronologicalOrderInSeries
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
B.
chronologicallyOrdered
chosen
Indicates that the related entities are arranged in the order in which they occur in time.
-
C.
chronologySeries
Indicates that one entity is part of, or defines, a chronological sequence or ordered series of events or items.
-
D.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
E.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5398fc81909f025bcccd0f80cb |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.