Triple
T17505421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natchez Trace Parkway Bridge |
E426300
|
entity |
| Predicate | archType |
P63910
|
FINISHED |
| Object | concrete tied arch |
—
|
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: concrete tied arch | Statement: [Natchez Trace Parkway Bridge, archType, concrete tied arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archType Context triple: [Natchez Trace Parkway Bridge, archType, concrete tied arch]
-
A.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
B.
hasArchType
chosen
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
C.
architectureName
Indicates the specific name or title assigned to an architecture.
-
D.
sideArchType
Indicates the architectural style or structural type used for the side arches in a construction or design.
-
E.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452159c28819084b2cba4313ddf28 |
completed | April 19, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.