Triple
T19995106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelations of Divine Love |
E494172
|
entity |
| Predicate | numberOfRevelations |
P138263
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Revelations of Divine Love, numberOfRevelations, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRevelations Context triple: [Revelations of Divine Love, numberOfRevelations, 16]
-
A.
typeOfRevelation
Indicates the specific manner or category of revelation through which information, truth, or insight is disclosed.
-
B.
orderOfRevelation
Indicates the sequence in which multiple related items, events, or pieces of information are revealed or disclosed.
-
C.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
-
D.
numberOfVisions
Indicates the quantity of visions experienced or associated with an entity.
-
E.
receivesRevelation
Indicates that one entity is the recipient of a divine, supernatural, or otherwise profound revelation originating from another source.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe306548190a6924ce3798a4d3d |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:31 p.m.