Triple
T22120729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chun’s Reef |
E546658
|
entity |
| Predicate | surfCrowdLevel |
P18989
|
FINISHED |
| Object | less crowded than nearby famous breaks |
—
|
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: less crowded than nearby famous breaks | Statement: [Chun’s Reef, surfCrowdLevel, less crowded than nearby famous breaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfCrowdLevel Context triple: [Chun’s Reef, surfCrowdLevel, less crowded than nearby famous breaks]
-
A.
hasCrowdLevel
chosen
Indicates the degree or intensity of how crowded a place, event, or situation is.
-
B.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
C.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
-
D.
visitorDemand
Indicates a relationship where the level or nature of demand expressed by visitors for something (e.g., a service, location, or resource) is specified or quantified.
-
E.
socialMobility
Indicates the degree to which individuals or groups can move between different social or economic status levels within a society over time.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12951fcd48190841319cd879c15cb |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.