Triple
T38673233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Beach |
E943657
|
entity |
| Predicate | amusementParkOperatedFrom |
P191509
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Crystal Beach, amusementParkOperatedFrom, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amusementParkOperatedFrom Context triple: [Crystal Beach, amusementParkOperatedFrom, 1888]
-
A.
amusementParkType
Indicates that one entity is classified as a specific type or category of amusement park in relation to another entity.
-
B.
themeParkStatus
Indicates the current operational condition or state of a theme park, such as whether it is open, closed, or otherwise restricted.
-
C.
themeParkPresence
Indicates that an entity is present at, located in, or associated with a theme park in the context of a given event or situation.
-
D.
themeParkOwner
Indicates that one entity owns, operates, or holds primary controlling interest in a theme park associated with the other entity.
-
E.
hasInfieldAmusementFacilities
Indicates that an entity provides or contains amusement or recreational facilities located within its infield area.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.