Triple
T21619890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Historical Civil Engineering Landmark |
E533547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil engineering landmark designation |
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: civil engineering landmark designation Context triple: [California Historical Civil Engineering Landmark, instanceOf, civil engineering landmark designation]
-
A.
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.
-
B.
civil engineering designation
A civil engineering designation is a formal title or credential that identifies a professional’s qualification, specialization, and authority to practice within the civil engineering field.
-
C.
engineering designation
An engineering designation is a formal title or credential that identifies an engineer’s professional qualification, specialization, and level of responsibility within the engineering field.
-
D.
structural engineering award
A structural engineering award is a formal recognition given to individuals, teams, or organizations for outstanding achievement, innovation, or excellence in the analysis, design, or construction of structural systems.
-
E.
cultural heritage designation
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:34 p.m.