Triple
T20117738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beggar on Horseback |
E490510
|
entity |
| Predicate | stageTechnique |
P73293
|
FINISHED |
| Object | stylized sets |
—
|
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: stylized sets | Statement: [Beggar on Horseback, stageTechnique, stylized sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageTechnique Context triple: [Beggar on Horseback, stageTechnique, stylized sets]
-
A.
stageTechnology
Indicates that a particular technology is used, implemented, or deployed at a specific stage or phase within a process, workflow, or lifecycle.
-
B.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
C.
hasDramaticTechnique
chosen
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
D.
stageDesigner
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
E.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6673ab4e08190b76ec742605e103b |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.