Triple
T27815419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blindfold Me |
E702646
|
entity |
| Predicate | hasNotableWorkCreator |
P127003
|
FINISHED |
| Object | Kelis |
—
|
NE NERFINISHED |
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: Kelis | Statement: [Blindfold Me, hasNotableWorkCreator, Kelis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWorkCreator Context triple: [Blindfold Me, hasNotableWorkCreator, Kelis]
-
A.
hasNotableAuthorWork
chosen
Indicates that an author is notably associated with creating a particular work.
-
B.
hasNotableWorkCategory
Indicates that an entity’s notable work belongs to, or is classified under, a particular category or type.
-
C.
hasNotableWorkExample
Indicates that an entity has a specific notable work cited as an example associated with it.
-
D.
hasNotableWorkSection
Indicates that a notable work is associated with a specific section or part of a larger work or document.
-
E.
hasNotableWorkCollection
Indicates that an entity is associated with a collection of its notable works or creations.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: April 27, 2026, 5:45 p.m.