Triple
T32476317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobu Group |
E829984
|
entity |
| Predicate | leisureBusinessType |
P40125
|
FINISHED |
| Object | theme parks |
—
|
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: theme parks | Statement: [Tobu Group, leisureBusinessType, theme parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leisureBusinessType Context triple: [Tobu Group, leisureBusinessType, theme parks]
-
A.
placeOfBusinessActivity
chosen
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
B.
recreationActivitiesSupported
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
-
C.
isRecreationalFacility
Indicates that the subject entity functions as a place or installation intended for leisure, sports, or other recreational activities.
-
D.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
venueConcept
Indicates a relationship where a venue is associated with, characterized by, or defined in terms of a particular concept or thematic idea.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3913f108190b2e10106534b6392 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:58 a.m.