Triple
T16462509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest (Six Flags Fiesta Texas) |
E399840
|
entity |
| Predicate | locatedInParkType |
P52905
|
FINISHED |
| Object | amusement 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: amusement park | Statement: [Southwest (Six Flags Fiesta Texas), locatedInParkType, amusement park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInParkType Context triple: [Southwest (Six Flags Fiesta Texas), locatedInParkType, amusement park]
-
A.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
B.
hasTypeOfPark
chosen
Indicates that an entity is associated with or classified by a specific type or category of park.
-
C.
isWithinPark
Indicates that one entity is located inside the boundaries of a park that contains it.
-
D.
locatedInParkLikeSetting
Indicates that something is situated within or directly surrounded by an environment resembling a park, typically featuring natural or landscaped outdoor elements.
-
E.
openedInPark
Indicates that an entity was opened, inaugurated, or began operating within the boundaries of a 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d824cd881909b1f2fd40e14ee35 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.