Triple
T26319456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-highway |
E662063
|
entity |
| Predicate | hasEngineeringStandard |
P107425
|
FINISHED |
| Object | designed for continuous high-speed flow |
—
|
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: designed for continuous high-speed flow | Statement: [M-highway, hasEngineeringStandard, designed for continuous high-speed flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringStandard Context triple: [M-highway, hasEngineeringStandard, designed for continuous high-speed flow]
-
A.
engineeringStandard
chosen
Indicates that something conforms to, is defined by, or is governed by a specified engineering standard or set of technical norms.
-
B.
hasProductionStandard
Indicates that something is governed, defined, or evaluated according to a specific production standard.
-
C.
hasEngineeringStyle
Indicates that an entity possesses or exhibits a particular engineering approach, methodology, or design style in how it is created, structured, or operates.
-
D.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
E.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 10:27 p.m.