Triple
T35422300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chocolate Fortress |
E1023826
|
entity |
| Predicate | secretExit |
P108779
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Chocolate Fortress, secretExit, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretExit Context triple: [Chocolate Fortress, secretExit, false]
-
A.
hasSecretExit
chosen
Indicates that something includes or is connected to a hidden or concealed way out.
-
B.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
C.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
-
D.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
E.
hasNumberOfFalseDoors
Indicates that an entity is associated with a specific count of false doors (door-like architectural features that do not function as actual entrances or exits).
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.