Triple
T1920547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Branch, New Jersey |
E40114
|
entity |
| Predicate | wasMajorResortFor |
P5644
|
FINISHED |
| Object | 19th-century visitors |
—
|
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: 19th-century visitors | Statement: [Long Branch, New Jersey, wasMajorResortFor, 19th-century visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorResortFor Context triple: [Long Branch, New Jersey, wasMajorResortFor, 19th-century visitors]
-
A.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
C.
majorPark
Indicates that a park is classified as a major or primary park within a given area or system.
-
D.
hasSpaResort
Indicates that one entity possesses, includes, or is associated with a spa resort as an amenity or feature.
-
E.
hasPopularResort
Indicates that a location or area contains or is associated with a resort that is widely visited or well-liked.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb213af0481909429ec971860a3fd |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.