Triple
T1473671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qutb |
E27191
|
entity |
| Predicate | epistemicAccess |
P16121
|
FINISHED |
| Object | known fully only to God in many teachings |
—
|
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: known fully only to God in many teachings | Statement: [qutb, epistemicAccess, known fully only to God in many teachings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epistemicAccess Context triple: [qutb, epistemicAccess, known fully only to God in many teachings]
-
A.
epistemicStatus
chosen
Indicates the degree of certainty, justification, or knowledge an agent has regarding a particular proposition or claim.
-
B.
viewOnKnowledge
Indicates the perspective, stance, or opinion one entity holds regarding another entity’s knowledge or understanding.
-
C.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
D.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
positionOnKnowledge
Indicates the stance, viewpoint, or level of agreement an entity holds regarding a particular piece or body of knowledge.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.