Triple
T5411000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ino |
E121010
|
entity |
| Predicate | afterlifeTransformation |
P44744
|
FINISHED |
| Object | sea deity |
—
|
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: sea deity | Statement: [Ino, afterlifeTransformation, sea deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterlifeTransformation Context triple: [Ino, afterlifeTransformation, sea deity]
-
A.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
B.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
C.
afterlifeForm
chosen
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
-
D.
coffinLaterBecomes
Indicates that something which is initially a coffin later transforms into or is repurposed as another object or state.
-
E.
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.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87985ee0819092a9a5cd6a948138 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.