Triple
T16333881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Bay Beach |
E396624
|
entity |
| Predicate | hasTypicalVisitors |
P74830
|
FINISHED |
| Object | cruise ship passengers on day trips |
—
|
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: cruise ship passengers on day trips | Statement: [Lower Bay Beach, hasTypicalVisitors, cruise ship passengers on day trips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalVisitors Context triple: [Lower Bay Beach, hasTypicalVisitors, cruise ship passengers on day trips]
-
A.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
B.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
C.
typicalVisitorsPerSeason
Indicates the usual number of visitors associated with each season for a given entity or location.
-
D.
typicalVisitorBehavior
Indicates the usual or characteristic way visitors act, respond, or interact in a given context or environment.
-
E.
typicalVisitorOrigin
chosen
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e1da1081909bec6e77e6109dce |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.