Triple
T4383447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape May Cafe |
E99183
|
entity |
| Predicate | isOnDisneyTransportationNetwork |
P14525
|
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: [Cape May Cafe, isOnDisneyTransportationNetwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnDisneyTransportationNetwork Context triple: [Cape May Cafe, isOnDisneyTransportationNetwork, true]
-
A.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
B.
transportationServedBy
chosen
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
-
D.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
-
E.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35262649c8190a724c9835cb7ece6 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.