Triple
T600779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway Visitor Park |
E11486
|
entity |
| Predicate | hasOpeningType |
P17856
|
FINISHED |
| Object | year-round attraction |
—
|
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: year-round attraction | Statement: [Runway Visitor Park, hasOpeningType, year-round attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningType Context triple: [Runway Visitor Park, hasOpeningType, year-round attraction]
-
A.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
B.
hasTextOpening
Indicates that an entity begins with or contains a specified initial segment of text.
-
C.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
- F. None of above. chosen
Provenance (4 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49cf701e08190966d06b9ff4b582b |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e55b2248190b0ae3d692c0fa143 |
completed | March 1, 2026, 8:15 p.m. |
Created at: March 1, 2026, 7:35 p.m.