Triple
T4373036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purple Haze |
E98939
|
entity |
| Predicate | laterIncludedOn |
P56452
|
FINISHED |
| Object | US edition of Are You Experienced |
—
|
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: US edition of Are You Experienced | Statement: [Purple Haze, laterIncludedOn, US edition of Are You Experienced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterIncludedOn Context triple: [Purple Haze, laterIncludedOn, US edition of Are You Experienced]
-
A.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
B.
laterReleased
Indicates that one entity was released at a time chronologically after the release of another entity.
-
C.
laterDeployedIn
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
-
D.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
E.
listedSince
Indicates the date or point in time since which an item, entity, or record has been officially listed or registered in a given context.
- F. None of above. chosen
Provenance (4 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521f7d9c81909c9209fe59d20ffd |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:17 p.m.