Triple
T26319448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-highway |
E662063
|
entity |
| Predicate | typicalDesignStandard |
P37655
|
FINISHED |
| Object | motorway standard |
—
|
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: motorway standard | Statement: [M-highway, typicalDesignStandard, motorway standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDesignStandard Context triple: [M-highway, typicalDesignStandard, motorway standard]
-
A.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
B.
designStandardizedIn
chosen
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
-
C.
typicalDesignElement
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
D.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
E.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
- 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_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 26, 2026, 10:27 p.m.