Triple
T31431298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agartha |
E801803
|
entity |
| Predicate | believedByOthersToBe |
P162829
|
FINISHED |
| Object | purely symbolic |
—
|
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: purely symbolic | Statement: [Agartha, believedByOthersToBe, purely symbolic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedByOthersToBe Context triple: [Agartha, believedByOthersToBe, purely symbolic]
-
A.
believedBySomeToBe
chosen
Indicates that at least some people hold the belief that one entity has a particular property, status, or relationship to another entity.
-
B.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
C.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
D.
believedToHave
Indicates that one entity is thought or assumed, but not confirmed, to possess or exhibit another entity or property.
-
E.
believedProvidedBy
Indicates that something is thought or assumed to have been supplied or made available by a particular source or provider.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 8:57 p.m.