Triple
T35421868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheese Bridge Area |
E1023816
|
entity |
| Predicate | normalExitLeadsTo |
P88382
|
FINISHED |
| Object | Cookie Mountain |
—
|
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: Cookie Mountain | Statement: [Cheese Bridge Area, normalExitLeadsTo, Cookie Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normalExitLeadsTo Context triple: [Cheese Bridge Area, normalExitLeadsTo, Cookie Mountain]
-
A.
normallyClosesAs
Indicates that one entity typically or by default closes or terminates in the state, condition, or configuration represented by another entity.
-
B.
exitTo
chosen
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
C.
normallyOperatesAs
Indicates that an entity’s usual or standard mode, role, or state of functioning is as the specified other entity or type.
-
D.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
E.
canonicalOutcome
Indicates that an event, process, or interaction leads to its standard, primary, or officially recognized result or consequence.
- 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_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.