Triple
T30152917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church |
E766440
|
entity |
| Predicate | behaviorAfterResurrection |
P86401
|
FINISHED |
| Object | more aggressive |
—
|
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: more aggressive | Statement: [Church, behaviorAfterResurrection, more aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorAfterResurrection Context triple: [Church, behaviorAfterResurrection, more aggressive]
-
A.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
B.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
C.
exhibitsAfterResurrection
chosen
Indicates that a subject displays or manifests a particular state, quality, or behavior following a resurrection event.
-
D.
conditionForResurrection
Indicates that a specified condition or set of conditions must be satisfied for a resurrection event to occur.
-
E.
methodOfResurrection
Indicates the specific process or means by which an entity is brought back to life or restored from death.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed5a87c8190b6d716ef7a34b957 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:20 p.m.