Triple
T20544124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Load and Resistance Factor Design |
E504419
|
entity |
| Predicate | designCheck |
P140491
|
FINISHED |
| Object | factored load effects ≤ factored resistance |
—
|
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: factored load effects ≤ factored resistance | Statement: [Load and Resistance Factor Design, designCheck, factored load effects ≤ factored resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCheck Context triple: [Load and Resistance Factor Design, designCheck, factored load effects ≤ factored resistance]
-
A.
designOutcome
Indicates the result, effect, or consequence produced by a particular design or design process.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
D.
designIssue
Indicates that there is a problem, flaw, or concern related to the design of an entity or system.
-
E.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
- F. None of above. chosen
Provenance (4 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a2957c308190aab81127f82f8aa6 |
completed | April 20, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.