Triple
T22920056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur – The Ride |
E568835
|
entity |
| Predicate | parkSectionOpeningDate |
P81515
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Arthur – The Ride, parkSectionOpeningDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkSectionOpeningDate Context triple: [Arthur – The Ride, parkSectionOpeningDate, 2014]
-
A.
parkSectionOpening
chosen
Indicates that a specific section of a park is opening or becoming available for use, typically at a particular time or under certain conditions.
-
B.
parkSectionOpeningWith
Indicates that a section of a park begins or is introduced with a specified feature, structure, or element.
-
C.
openingDateAsPark
Indicates the date on which a place or area was first officially opened and began operating as a park.
-
D.
cityParkStatus
Indicates the current operational or accessibility status of a city park in relation to its governing jurisdiction or management.
-
E.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d40f98819096210c097b47d43b |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.