Triple
T30152912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church |
E766440
|
entity |
| Predicate | reanimatedBy |
P7738
|
FINISHED |
| Object | Micmac burial ground |
—
|
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: Micmac burial ground | Statement: [Church, reanimatedBy, Micmac burial ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reanimatedBy Context triple: [Church, reanimatedBy, Micmac burial ground]
-
A.
revivedBy
chosen
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
B.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
C.
reprogrammedBy
Indicates that an entity’s original programming or code has been altered or replaced by another specified agent or process.
-
D.
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.
-
E.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
- 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_69f67ed4df5081908d1431e3a1a1fb0e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.