Triple
T34455455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Hearing |
E884491
|
entity |
| Predicate | denotesPerfectionIn |
P73729
|
FINISHED |
| Object | Divine hearing |
—
|
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: Divine hearing | Statement: [All-Hearing, denotesPerfectionIn, Divine hearing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesPerfectionIn Context triple: [All-Hearing, denotesPerfectionIn, Divine hearing]
-
A.
perfectionPracticed
Indicates that an entity actively engages in or applies practices aimed at achieving or maintaining perfection.
-
B.
isTotallyPerfect
Indicates that an entity possesses complete flawlessness or ideal qualities in every relevant aspect.
-
C.
isPerfect
chosen
Indicates that an entity possesses all required qualities or characteristics to the highest or complete degree, without flaws or deficiencies.
-
D.
denotesDignity
Indicates that one entity confers, expresses, or is associated with the dignity or honorable status of another entity.
-
E.
viewOnPerfection
Indicates a subject’s stance, belief, or interpretation regarding the nature or attainability of perfection.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71976c49c8190943046a0ff8950cb |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.