Triple
T16142345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Long Branch |
E391688
|
entity |
| Predicate | isHistoricSeasideResort |
P73235
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [City of Long Branch, isHistoricSeasideResort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricSeasideResort Context triple: [City of Long Branch, isHistoricSeasideResort, true]
-
A.
isSeasideResort
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
B.
isSeasideVillage
Indicates that a village is located directly by the sea or coastline.
-
C.
hasHistoricResortOrigin
chosen
Indicates that something originated as, or was originally established for use as, a historic resort.
-
D.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
E.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9082588190bc7e6ff491f0d94e |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.