Triple
T5230698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AASHTO LRFD Bridge Design Specifications |
E118102
|
entity |
| Predicate | basisOfDesign |
P7125
|
FINISHED |
| Object | limit states design |
—
|
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: limit states design | Statement: [AASHTO LRFD Bridge Design Specifications, basisOfDesign, limit states design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfDesign Context triple: [AASHTO LRFD Bridge Design Specifications, basisOfDesign, limit states design]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
C.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0093a88190aba381ba3f761408 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.