Triple
T1943490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware Aqueduct |
E42008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic civil engineering structure |
C3635
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic civil engineering structure Context triple: [Delaware Aqueduct, instanceOf, historic civil engineering structure]
-
A.
historic infrastructure
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
-
B.
civil engineering landmark
chosen
A civil engineering landmark is a significant structure or project—such as a bridge, dam, tunnel, or roadway—that exemplifies notable achievement, innovation, or historical importance in the field of civil engineering.
-
C.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
D.
historic institution
A historic institution is an established organization or structure that has played a significant, enduring role in society over time and is recognized for its cultural, political, or social legacy.
-
E.
historic maritime signal tower
A historic maritime signal tower is a coastal structure once used to communicate navigational information, warnings, and messages to ships at sea through visual signals such as flags, lights, or semaphores.
- F. None of above.
Provenance (1 batch)
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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.