Triple
T15162532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akashic records |
E362253
|
entity |
| Predicate | regardedByScienceAs |
P88404
|
FINISHED |
| Object | unverified |
—
|
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: unverified | Statement: [Akashic records, regardedByScienceAs, unverified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardedByScienceAs Context triple: [Akashic records, regardedByScienceAs, unverified]
-
A.
consideredByScience
chosen
Indicates that something is regarded, evaluated, or treated as valid or relevant within the framework, methods, or consensus of scientific inquiry.
-
B.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
C.
hasScience
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
-
D.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
E.
hasScientificValue
Indicates that something possesses significance, usefulness, or merit within scientific research, understanding, or methodology.
- 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_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. |
Created at: April 10, 2026, 3:08 a.m.