Triple
T1639804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coney Island |
E35441
|
entity |
| Predicate | developedAsAmusementArea |
P30834
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Coney Island, developedAsAmusementArea, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsAmusementArea Context triple: [Coney Island, developedAsAmusementArea, late 19th century]
-
A.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
-
C.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
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.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:28 p.m.