Triple
T9425803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanity 6 |
E227260
|
entity |
| Predicate | stageShowCharacteristic |
P69560
|
FINISHED |
| Object | provocative image |
—
|
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: provocative image | Statement: [Vanity 6, stageShowCharacteristic, provocative image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageShowCharacteristic Context triple: [Vanity 6, stageShowCharacteristic, provocative image]
-
A.
stagePortrayalIncludes
chosen
Indicates that a stage portrayal incorporates or features a particular element, character, action, or aspect within the performance.
-
B.
hasStageAppearance
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
C.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
D.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
E.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c908738819081df35c632f35f04 |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.