Triple
T14125310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea View Beach |
E340013
|
entity |
| Predicate | hasTimeOfHighVisitorTraffic |
P86087
|
FINISHED |
| Object | evenings |
—
|
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: evenings | Statement: [Sea View Beach, hasTimeOfHighVisitorTraffic, evenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOfHighVisitorTraffic Context triple: [Sea View Beach, hasTimeOfHighVisitorTraffic, evenings]
-
A.
hasHeavyPassengerTraffic
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
B.
hasHeavyTraffic
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
C.
hasTimeOfHighActivity
chosen
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
D.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
E.
hasDailyPassengerTraffic
Indicates the number of passengers that regularly use or pass through something (such as a station or route) each day.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.