Triple
T13915049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Tau |
E334599
|
entity |
| Predicate | hasEsotericMeaning |
P58343
|
FINISHED |
| Object | name of God concealed |
—
|
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: name of God concealed | Statement: [Triple Tau, hasEsotericMeaning, name of God concealed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEsotericMeaning Context triple: [Triple Tau, hasEsotericMeaning, name of God concealed]
-
A.
esotericLevel
chosen
Indicates the degree to which something is obscure, specialized, or understandable only to a small, knowledgeable group.
-
B.
hasIronicMeaning
Indicates that something conveys a meaning opposite to or incongruent with its literal expression, creating an ironic effect.
-
C.
esotericStructure
Indicates a relationship in which something has a hidden, obscure, or specialized internal organization or pattern that is not readily apparent to most observers.
-
D.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
-
E.
hasMeaningCategory
Indicates that something is associated with a particular category of meaning or semantic type.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.