Triple
T19957028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandish |
E479710
|
entity |
| Predicate | hasRoadImprovements |
P138018
|
FINISHED |
| Object | widened for safety |
—
|
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: widened for safety | Statement: [Brandish, hasRoadImprovements, widened for safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadImprovements Context triple: [Brandish, hasRoadImprovements, widened for safety]
-
A.
hasRoadImprovementProject
Indicates that there is a planned, ongoing, or completed project aimed at improving or upgrading a road or roadway infrastructure between the related entities.
-
B.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
C.
hasPermanentRoads
Indicates that an entity possesses roads that are constructed to be durable and remain in place over an extended period, rather than being temporary or seasonal.
-
D.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
- F. None of above. chosen
Provenance (4 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af08e008190a3a1b807b638a99e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.