Triple
T35533099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Plains 2 |
E1026856
|
entity |
| Predicate | unlocksViaNormalExit |
P183211
|
FINISHED |
| Object | Donut Ghost House |
—
|
NE NERFINISHED |
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: Donut Ghost House | Statement: [Donut Plains 2, unlocksViaNormalExit, Donut Ghost House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlocksViaNormalExit Context triple: [Donut Plains 2, unlocksViaNormalExit, Donut Ghost House]
-
A.
normallyClosesAs
Indicates that one entity typically or by default closes or terminates in the state, condition, or configuration represented by another entity.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
previousSystemClosed
Indicates that a prior system, session, or process has been properly terminated or closed before the current context.
-
D.
hasNumberedExit
Indicates that an entity (such as a road or highway) includes or is associated with an exit that has an assigned number.
-
E.
cordExit
Indicates that a cord or cable leads out from, terminates at, or exits a particular object or location.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.