Triple
T21126613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordinalia |
E520572
|
entity |
| Predicate | containsStageDirections |
P114800
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ordinalia, containsStageDirections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStageDirections Context triple: [Ordinalia, containsStageDirections, true]
-
A.
hasStageDirections
chosen
Indicates that a dramatic work or script includes explicit stage directions describing actions, movements, or settings.
-
B.
includesFamousStageDirection
Indicates that the subject contains or features a well-known or widely recognized stage direction within it.
-
C.
stageDirectionDescription
Indicates a textual description of how an action, movement, or expression should be performed or presented within a staged or scripted context.
-
D.
stageDirectionName
Indicates the specific label or term used to identify a particular stage direction within a performance or script.
-
E.
directedStageProduction
Indicates that one entity served as the director responsible for staging and overseeing a particular theatrical or stage production involving 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72239965c819081b4077b914d0a98 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.