Triple
T10032073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misirlou |
E204874
|
entity |
| Predicate | notableArrangementYear |
P87190
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Misirlou, notableArrangementYear, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArrangementYear Context triple: [Misirlou, notableArrangementYear, 1962]
-
A.
notableArrangementType
Indicates that one entity is characterized by or associated with a particular notable type of arrangement or configuration of another entity.
-
B.
musicArrangedYear
chosen
Indicates the year in which a piece of music was arranged or re-arranged into its specific version.
-
C.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
D.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
E.
notablePerformanceYear
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce461d6481908cc8f968856e0337 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.