Triple
T17516446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franconia Notch Parkway |
E426579
|
entity |
| Predicate | designCompromiseFor |
P127723
|
FINISHED |
| Object | preservation of Franconia Notch |
—
|
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: preservation of Franconia Notch | Statement: [Franconia Notch Parkway, designCompromiseFor, preservation of Franconia Notch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCompromiseFor Context triple: [Franconia Notch Parkway, designCompromiseFor, preservation of Franconia Notch]
-
A.
designOutcome
Indicates the result, effect, or consequence produced by a particular design or design process.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
- F. None of above. chosen
Provenance (4 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4526097388190ba1a949064962a24 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.