Triple
T30172014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinzua Bridge State Park |
E766944
|
entity |
| Predicate | skywalkBuiltOn |
P2012
|
FINISHED |
| Object | remaining Kinzua Viaduct towers |
—
|
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: remaining Kinzua Viaduct towers | Statement: [Kinzua Bridge State Park, skywalkBuiltOn, remaining Kinzua Viaduct towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skywalkBuiltOn Context triple: [Kinzua Bridge State Park, skywalkBuiltOn, remaining Kinzua Viaduct towers]
-
A.
skywalkFeature
Indicates a relationship where one location or structure is connected to another by an elevated, typically enclosed pedestrian walkway (skywalk).
-
B.
skywalkOpened
Indicates that a skywalk has been officially opened for use or made accessible.
-
C.
builtOn
chosen
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
D.
skylineType
Indicates the general visual or structural character of a skyline, such as its dominant form, density, or profile.
-
E.
hasSkyway
Indicates that there is an elevated, usually enclosed walkway or bridge connecting two or more structures or areas.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0c2d248190a12c361305d6f00d |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:24 p.m.