Triple
T12782730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Velvet Bulldozer |
E305546
|
entity |
| Predicate | describesStagePresence |
P102598
|
FINISHED |
| Object | imposing |
—
|
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: imposing | Statement: [The Velvet Bulldozer, describesStagePresence, imposing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesStagePresence Context triple: [The Velvet Bulldozer, describesStagePresence, imposing]
-
A.
hasStageAppearance
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
B.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
scenePresence
chosen
Indicates that an entity is present or appears within a particular scene or context.
-
E.
stageName
Indicates that one entity is the performance or professional name used by another entity.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5b52048190b279b7ad066efe9f |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.