Triple
T13881157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liliom |
E333718
|
entity |
| Predicate | hasStageDirectionStyle |
P35532
|
FINISHED |
| Object | naturalistic |
—
|
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: naturalistic | Statement: [Liliom, hasStageDirectionStyle, naturalistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageDirectionStyle Context triple: [Liliom, hasStageDirectionStyle, naturalistic]
-
A.
includesFamousStageDirection
Indicates that the subject contains or features a well-known or widely recognized stage direction within it.
-
B.
stageDirectionDescription
Indicates a textual description of how an action, movement, or expression should be performed or presented within a staged or scripted context.
-
C.
stagingStyle
chosen
Indicates how an event, performance, or scene is arranged, presented, or visually organized in a given context.
-
D.
hasStructuralStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
E.
hasInterpretationStyle
Indicates a relationship where an entity is associated with a particular manner, method, or style in which it is interpreted or understood.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.