Triple
T19775821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dedication of the Temple |
E474998
|
entity |
| Predicate | causesReaction |
P97670
|
FINISHED |
| Object | priests unable to stand to minister |
—
|
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: priests unable to stand to minister | Statement: [Dedication of the Temple, causesReaction, priests unable to stand to minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesReaction Context triple: [Dedication of the Temple, causesReaction, priests unable to stand to minister]
-
A.
causedReaction
chosen
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
B.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
-
C.
isAReactionTo
Indicates that one event, action, or state occurs as a direct response or consequence of another.
-
D.
featuresReaction
Indicates that one entity exhibits, displays, or includes a particular reaction associated with another entity or context.
-
E.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535fb114819089911ed3ba6565c0 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.