Triple
T35595395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Secret 3 |
E1028616
|
entity |
| Predicate | hasNormalExitTo |
P207059
|
FINISHED |
| Object | Donut Secret House |
E1023806
|
NE 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: Donut Secret House | Statement: [Donut Secret 3, hasNormalExitTo, Donut Secret House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNormalExitTo Context triple: [Donut Secret 3, hasNormalExitTo, Donut Secret House]
-
A.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
B.
hasNumberedExit
Indicates that an entity (such as a road or highway) includes or is associated with an exit that has an assigned number.
-
C.
hasExitList
Indicates that an entity is associated with a collection of defined exits or exit points.
-
D.
isMajorExitOf
Indicates that one location serves as a primary or significant exit point from another location or route.
-
E.
unlocksViaNormalExit
Indicates that something becomes unlocked when a standard or regular exit is used.
- F. None of above. chosen
Provenance (5 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_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387273f5888190acb5590f1e2c9a73 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.