Triple
T11907016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boneyard |
E283295
|
entity |
| Predicate | immersiveEnvironment |
P30765
|
FINISHED |
| Object | prehistoric setting |
—
|
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: prehistoric setting | Statement: [The Boneyard, immersiveEnvironment, prehistoric setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immersiveEnvironment Context triple: [The Boneyard, immersiveEnvironment, prehistoric setting]
-
A.
immersesVisitorsIn
chosen
Indicates that one entity deeply involves or surrounds visitors in an experience, environment, or atmosphere created by another entity.
-
B.
hasVirtualExperience
Indicates that one entity possesses or has participated in a virtual or digitally simulated experience related to another entity.
-
C.
intendedViewerExperience
Indicates the type or quality of experience that a piece of content is designed or expected to provide to its viewers.
-
D.
ambientSpace
Indicates the surrounding or containing space within which an object, structure, or geometric entity is situated or defined.
-
E.
viewOnReality
Indicates a subject’s overarching perspective, interpretation, or conceptual stance regarding the nature of reality.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5264b2081909bda6c24abb89725 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.