Triple
T31419428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The All-Seeing |
E801488
|
entity |
| Predicate | grantsReputationAs |
P179251
|
FINISHED |
| Object | omniscient mystical being |
—
|
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: omniscient mystical being | Statement: [The All-Seeing, grantsReputationAs, omniscient mystical being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsReputationAs Context triple: [The All-Seeing, grantsReputationAs, omniscient mystical being]
-
A.
grantsRecognitionTo
Indicates that one entity formally acknowledges, honors, or validates another entity’s achievements, status, or contributions.
-
B.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
-
C.
grantedAsRewardFor
Indicates that something is given to an entity specifically as a reward for a particular action, achievement, or service.
-
D.
grantedAs
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to another entity.
-
E.
confersRecognition
Indicates that one entity formally acknowledges, honors, or grants recognition to another entity for some quality, status, or achievement.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 30, 2026, 8:46 p.m.