Triple
T12195343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammit |
E290571
|
entity |
| Predicate | consequenceOfEncounter |
P98798
|
FINISHED |
| Object | destruction of the soul |
—
|
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: destruction of the soul | Statement: [Ammit, consequenceOfEncounter, destruction of the soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfEncounter Context triple: [Ammit, consequenceOfEncounter, destruction of the soul]
-
A.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
C.
significantEventConsequence
chosen
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
-
D.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
E.
notableEncounterWith
Indicates that an entity has had a significant or noteworthy meeting, interaction, or confrontation with 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.