Triple
T35595412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Secret 3 |
E1028616
|
entity |
| Predicate | hasSecretExitCondition |
P201753
|
FINISHED |
| Object | finding hidden key and keyhole |
—
|
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: finding hidden key and keyhole | Statement: [Donut Secret 3, hasSecretExitCondition, finding hidden key and keyhole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretExitCondition Context triple: [Donut Secret 3, hasSecretExitCondition, finding hidden key and keyhole]
-
A.
hasSecretExit
Indicates that something includes or is connected to a hidden or concealed way out.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
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.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
| PDg | Predicate description generation | batch_6a001adbe6588190b7af521508b18898 |
completed | May 10, 2026, 5:42 a.m. |
Created at: May 3, 2026, 4:05 p.m.