Triple
T15162518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akashic records |
E362253
|
entity |
| Predicate | claimedToExistIn |
P116976
|
FINISHED |
| Object | non-physical plane |
—
|
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: non-physical plane | Statement: [Akashic records, claimedToExistIn, non-physical plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedToExistIn Context triple: [Akashic records, claimedToExistIn, non-physical plane]
-
A.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
D.
claimedToCorrect
Indicates that one entity asserted or stated that it would fix, rectify, or correct another entity or its content.
-
E.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
- F. None of above. chosen
Provenance (4 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060f2efc8190aa0eb5fb8d4ce085 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:08 a.m.