Triple
T10324143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky "Jupe" Park |
E242716
|
entity |
| Predicate | themeOfBusiness |
P25955
|
FINISHED |
| Object | Western-themed amusement park |
—
|
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: Western-themed amusement park | Statement: [Ricky "Jupe" Park, themeOfBusiness, Western-themed amusement park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfBusiness Context triple: [Ricky "Jupe" Park, themeOfBusiness, Western-themed amusement park]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
businessPlanSubject
Indicates that one entity is the subject or main focus of a business plan associated with another entity.
-
C.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
-
E.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.