Triple
T13148625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanilla Dome |
E312403
|
entity |
| Predicate | hasSecretExit |
P108779
|
FINISHED |
| Object | Vanilla Dome 1 secret exit |
—
|
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: Vanilla Dome 1 secret exit | Statement: [Vanilla Dome, hasSecretExit, Vanilla Dome 1 secret exit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretExit Context triple: [Vanilla Dome, hasSecretExit, Vanilla Dome 1 secret exit]
-
A.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
B.
hasNearbyExit
Indicates that one entity has an exit located close to it in space or distance.
-
C.
hasSouthExit
Indicates that an entity has an exit or passage leading toward the south.
-
D.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
E.
containsSecretRoomCount
Indicates that an entity has a specified number of secret rooms contained within it.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:11 p.m.