Triple
T14855004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mikvaot |
E349328
|
entity |
| Predicate | typicalImmersionType |
P115881
|
FINISHED |
| Object | full-body immersion |
—
|
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: full-body immersion | Statement: [mikvaot, typicalImmersionType, full-body immersion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImmersionType Context triple: [mikvaot, typicalImmersionType, full-body immersion]
-
A.
immersedIn
Indicates that one entity is fully surrounded, absorbed, or deeply involved within another medium, environment, or activity.
-
B.
immersive
Indicates that an experience or environment fully surrounds and engages an entity’s senses or attention, creating a strong feeling of being present within it.
-
C.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
D.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
E.
immersesVisitorsIn
Indicates that one entity deeply involves or surrounds visitors in an experience, environment, or atmosphere created by another entity.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.