Triple
T20163775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oblivion |
E491777
|
entity |
| Predicate | themeParkType |
P80066
|
FINISHED |
| Object | amusement park 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: amusement park attraction | Statement: [Oblivion, themeParkType, amusement park attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeParkType Context triple: [Oblivion, themeParkType, amusement park attraction]
-
A.
themeParkAttraction
chosen
Indicates that something is an attraction or ride located within a theme park.
-
B.
themeParkComplex
Indicates a relationship where one entity is a theme park complex that encompasses or is composed of the other entity or entities.
-
C.
themeParkAttractionAt
Indicates that a specific theme park attraction is located at or associated with a particular theme park or site.
-
D.
themeParkConnection
Indicates a relationship where two or more entities are connected through a theme park, such as by location, operation, partnership, or shared attractions.
-
E.
themeParkAttractionLocation
Indicates the specific place or area within a theme park where a particular attraction is situated.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66841b7d88190af3606f762d87b24 |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.