Triple
T2738759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niagara Falls Suspension Bridge |
E60694
|
entity |
| Predicate | engineeringDiscipline |
P15961
|
FINISHED |
| Object | civil engineering |
—
|
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: civil engineering | Statement: [Niagara Falls Suspension Bridge, engineeringDiscipline, civil engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringDiscipline Context triple: [Niagara Falls Suspension Bridge, engineeringDiscipline, civil engineering]
-
A.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
-
B.
hasEngineeringSignificance
chosen
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
C.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
-
D.
architecture
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
-
E.
hasStructuralEngineer
Indicates that an entity is associated with or employs a structural engineer responsible for its structural design, analysis, or integrity.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb147a588190829b74fe05b3a114 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.