Triple
T4193639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Religion of Humanity |
E89091
|
entity |
| Predicate | regards |
P54588
|
FINISHED |
| Object | humanity as the supreme moral reference |
—
|
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: humanity as the supreme moral reference | Statement: [Religion of Humanity, regards, humanity as the supreme moral reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regards Context triple: [Religion of Humanity, regards, humanity as the supreme moral reference]
-
A.
regardsSufferingAs
Indicates how an entity perceives, evaluates, or emotionally responds to the suffering of another entity.
-
B.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
E.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af04af4e44819098a9d7f91e65adf2 |
completed | March 9, 2026, 5:34 p.m. |
Created at: March 9, 2026, 3:46 p.m.