Triple
T36503894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil Woman |
E899408
|
entity |
| Predicate | hasNotableAside |
P204904
|
FINISHED |
| Object | B-side to hit single You're Sixteen |
—
|
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: B-side to hit single You're Sixteen | Statement: [Devil Woman, hasNotableAside, B-side to hit single You're Sixteen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAside Context triple: [Devil Woman, hasNotableAside, B-side to hit single You're Sixteen]
-
A.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
C.
hasNotableSentence
Indicates that an entity is associated with a particularly important, famous, or otherwise noteworthy sentence.
-
D.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
-
E.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.