Triple
T19761453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Kennywood |
E474638
|
entity |
| Predicate | hasPathwayConnection |
P27773
|
FINISHED |
| Object | Kennywood main midway |
—
|
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: Kennywood main midway | Statement: [Lost Kennywood, hasPathwayConnection, Kennywood main midway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPathwayConnection Context triple: [Lost Kennywood, hasPathwayConnection, Kennywood main midway]
-
A.
hasPathway
chosen
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
B.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
hasCausewayConnection
Indicates a relationship where two locations are physically linked by a causeway, allowing passage between them.
-
E.
supportsPathway
Indicates that one entity contributes to, enables, or maintains the functioning or progression of a specified pathway.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6532004d08190944234d35e74085b |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.