Triple
T15162860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Secret Doctrine |
E362259
|
entity |
| Predicate | claimsSource |
P116977
|
FINISHED |
| Object | ancient wisdom tradition |
—
|
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: ancient wisdom tradition | Statement: [The Secret Doctrine, claimsSource, ancient wisdom tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsSource Context triple: [The Secret Doctrine, claimsSource, ancient wisdom tradition]
-
A.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
B.
claimMethod
Indicates the method or procedure by which a claim is made, submitted, or executed.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
claimsEffect
Indicates that one entity asserts or states that another entity has a particular effect or impact.
-
E.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
- 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_69e0064b21ac81908b793bdbd741bcd8 |
completed | April 15, 2026, 9:42 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.