Triple
T29202567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton Bridge |
E740318
|
entity |
| Predicate | isKeyRegionalCrossing |
P33204
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Grafton Bridge, isKeyRegionalCrossing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyRegionalCrossing Context triple: [Grafton Bridge, isKeyRegionalCrossing, true]
-
A.
isRegionalCrossroads
Indicates that a place serves as a key junction where multiple regional routes, networks, or areas intersect and connect.
-
B.
isKeyCrossingFor
chosen
Indicates that one entity serves as a primary or critical crossing point (such as a bridge, intersection, or passage) for another entity’s movement or connectivity.
-
C.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
D.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
E.
haveCrossBorderCorridor
Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 12:07 p.m.