Triple
T34513706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Angel |
E886090
|
entity |
| Predicate | centralToScene |
P130176
|
FINISHED |
| Object | Prior’s hospital visitation |
—
|
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: Prior’s hospital visitation | Statement: [The Angel, centralToScene, Prior’s hospital visitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToScene Context triple: [The Angel, centralToScene, Prior’s hospital visitation]
-
A.
centralScene
Indicates that one scene functions as the main or focal scene within a larger narrative, sequence, or composition.
-
B.
sceneCenter
chosen
Indicates that one entity serves as the central or focal point of a scene in relation to another entity.
-
C.
centralToMovement
Indicates that something plays a core, defining, or organizing role within a particular movement or collective effort.
-
D.
coordinateTransformation
Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
-
E.
centralToArcOf
Indicates that one entity lies at the geometric center or midpoint of an arc defined 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 2:01 a.m.