Triple
T35421869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheese Bridge Area |
E1023816
|
entity |
| Predicate | requiresYoshiForSecretExit |
P200760
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cheese Bridge Area, requiresYoshiForSecretExit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresYoshiForSecretExit Context triple: [Cheese Bridge Area, requiresYoshiForSecretExit, true]
-
A.
hasSecretExit
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.
unlocksViaSecretExit
Indicates that access to something becomes available specifically through the use of a hidden or secret exit.
-
D.
hasHiddenEntrance
Indicates that an entity possesses a concealed or non-obvious entrance or access point.
-
E.
seeksSecretFrom
Indicates that one entity is actively trying to obtain hidden or confidential information from 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69ffab59fe408190b72f13016de9953c |
completed | May 9, 2026, 9:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.