Triple
T11743413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalon, New Jersey |
E279209
|
entity |
| Predicate | summerTourismType |
P1769
|
FINISHED |
| Object | family-oriented tourism |
—
|
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: family-oriented tourism | Statement: [Avalon, New Jersey, summerTourismType, family-oriented tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerTourismType Context triple: [Avalon, New Jersey, summerTourismType, family-oriented tourism]
-
A.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
-
B.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
D.
tourismEvent
Indicates an event or activity that is organized for or significantly involves tourism, attracting visitors for leisure, cultural, or recreational purposes.
-
E.
summerFeature
Indicates that something is a characteristic, attraction, or condition specifically associated with or prominent during the summer season.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.