Triple
T33754185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-6N |
E864926
|
entity |
| Predicate | firstPublicRevelation |
—
|
GENERATED |
| Object | 2019 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicRevelation Context triple: [H-6N, firstPublicRevelation, 2019]
-
A.
firstPublicRevelationsBy
Indicates that the subject is the entity that first publicly revealed or disclosed the object.
-
B.
deliveredFirstRevelationTo
Indicates that one entity was the initial recipient of a first divine, prophetic, or otherwise foundational revelation communicated by another entity.
-
C.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
-
D.
firstRevelationPlace
Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
-
E.
firstRevelationNear
Indicates that an entity’s initial revelation, disclosure, or divine communication occurred in the vicinity of a specified place or reference entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.