Triple
T5230747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AASHTO Green Book |
E118103
|
entity |
| Predicate | definesStandardFor |
P30412
|
FINISHED |
| Object | design speed |
—
|
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: design speed | Statement: [AASHTO Green Book, definesStandardFor, design speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStandardFor Context triple: [AASHTO Green Book, definesStandardFor, design speed]
-
A.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
-
B.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
C.
developsStandardsFor
chosen
Indicates that one entity creates, defines, or establishes formal standards, guidelines, or specifications for another entity or domain.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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.