Triple
T29453431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Garden (Odesa) |
E747036
|
entity |
| Predicate | mainTypeOfAttraction |
P8077
|
FINISHED |
| Object | city 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: city park | Statement: [City Garden (Odesa), mainTypeOfAttraction, city park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTypeOfAttraction Context triple: [City Garden (Odesa), mainTypeOfAttraction, city park]
-
A.
attractionType
chosen
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
B.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
C.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
D.
ridesAttraction
Indicates that an entity participates in experiencing or using an attraction, such as going on a ride at a venue or amusement location.
-
E.
attractionTypeContext
Indicates the specific situational or contextual conditions under which an attraction between entities holds or is characterized.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 3:34 p.m.