Triple
T23023640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmar Seafood Festival |
E573236
|
entity |
| Predicate | transportationOptions |
P113640
|
FINISHED |
| Object | shuttle service |
—
|
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: shuttle service | Statement: [Belmar Seafood Festival, transportationOptions, shuttle service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationOptions Context triple: [Belmar Seafood Festival, transportationOptions, shuttle service]
-
A.
transportOptions
chosen
Indicates the available means or methods by which something or someone can be transported from one place to another.
-
B.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
D.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847b86688190b678d0d09ecd3c3d |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.