Triple
T36091794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hell Not Hallelujah Tour |
E1043937
|
entity |
| Predicate | hasApproximateTimePeriod |
P115721
|
FINISHED |
| Object | mid-2010s |
—
|
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: mid-2010s | Statement: [The Hell Not Hallelujah Tour, hasApproximateTimePeriod, mid-2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateTimePeriod Context triple: [The Hell Not Hallelujah Tour, hasApproximateTimePeriod, mid-2010s]
-
A.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
B.
timePeriodApproximation
chosen
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
C.
activePeriodApproximate
Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:08 p.m.