Triple
T20903920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A58 motorway |
E514742
|
entity |
| Predicate | hasRoadSignPrefix |
P78873
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [A58 motorway, hasRoadSignPrefix, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSignPrefix Context triple: [A58 motorway, hasRoadSignPrefix, A]
-
A.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
B.
roadSignPrefix
chosen
Indicates a relationship where one element serves as the initial or leading part of a road sign’s text, code, or designation.
-
C.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
-
D.
hasRoadTypePrefix
Indicates that a road-related identifier or name begins with a specific road type prefix (such as "Highway", "Route", or "Street").
-
E.
hasRoadSignShape
Indicates that one entity possesses or exhibits the geometric shape characteristic of a particular road sign.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fe4b808190bbc1bbde7a11f283 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.