Triple
T36411509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act IV |
E896890
|
entity |
| Predicate | structuralImportance |
P102539
|
FINISHED |
| Object | pivotal section of the play |
—
|
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: pivotal section of the play | Statement: [Act IV, structuralImportance, pivotal section of the play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralImportance Context triple: [Act IV, structuralImportance, pivotal section of the play]
-
A.
significantStructureWithin
chosen
Indicates that one structure is an important or notable part located inside another structure.
-
B.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
C.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
D.
visualImportance
Indicates how visually prominent or attention‑drawing one entity is relative to others in a given context.
-
E.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.