Triple
T9628146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborn Engineering Company |
E232522
|
entity |
| Predicate | structuralFocus |
P71761
|
FINISHED |
| Object | steel structures |
—
|
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: steel structures | Statement: [Osborn Engineering Company, structuralFocus, steel structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralFocus Context triple: [Osborn Engineering Company, structuralFocus, steel structures]
-
A.
structureFocus
chosen
Indicates that attention or emphasis is placed on the structural aspects or organization of something within the described context.
-
B.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
-
C.
structuralTrend
Indicates the predominant directional orientation or pattern of a structure relative to a reference frame or axis.
-
D.
structuralIssues
Indicates that there are problems or deficiencies in the design, construction, or integrity of a structure or system.
-
E.
majorStructure
Indicates that one entity functions as a primary or principal structural component or framework in relation to another entity.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.