Triple
T36772887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chip ‘n’ Dale’s Campfire Sing-A-Long |
E908527
|
entity |
| Predicate | requiresTicketToResort |
P46100
|
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: [Chip ‘n’ Dale’s Campfire Sing-A-Long, requiresTicketToResort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTicketToResort Context triple: [Chip ‘n’ Dale’s Campfire Sing-A-Long, requiresTicketToResort, true]
-
A.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
B.
requiresPermitOrReservation
Indicates that performing the associated activity or accessing the related resource is conditional on obtaining a permit or making a reservation in advance.
-
C.
requiresParkTicket
chosen
Indicates that access to something is conditional on possessing a valid park ticket.
-
D.
hasResortAccessTo
Indicates that one entity is permitted to use, enter, or benefit from the facilities or services of a particular resort.
-
E.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:12 p.m.