Triple
T21245783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divine Presence |
E523603
|
entity |
| Predicate | experiencedIn |
P141157
|
FINISHED |
| Object | world |
—
|
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: world | Statement: [Divine Presence, experiencedIn, world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedIn Context triple: [Divine Presence, experiencedIn, world]
-
A.
hasExperienceOf
chosen
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
B.
experienceIncludes
Indicates that a particular experience encompasses, contains, or involves a specified component, activity, or element as part of it.
-
C.
allegedlyExperienced
Indicates that an entity is claimed or reported to have undergone or had a particular experience, without asserting that the experience actually occurred.
-
D.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73599e5548190ad70d2c2bfa9e919 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:49 p.m.