Triple
T164861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania-Reading Seashore Lines |
E2990
|
entity |
| Predicate | servedDestinationType |
P2066
|
FINISHED |
| Object | seashore resorts |
—
|
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: seashore resorts | Statement: [Pennsylvania-Reading Seashore Lines, servedDestinationType, seashore resorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDestinationType Context triple: [Pennsylvania-Reading Seashore Lines, servedDestinationType, seashore resorts]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
isDestinationFor
chosen
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
C.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
D.
servedCity
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
E.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258827da481909b20ea5e9d21676f |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.