Triple
T9047626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soham |
E216796
|
entity |
| Predicate | hasNearbyTransportCorridor |
P25143
|
FINISHED |
| Object | A142 road |
—
|
NE NERFINISHED |
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: A142 road | Statement: [Soham, hasNearbyTransportCorridor, A142 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTransportCorridor Context triple: [Soham, hasNearbyTransportCorridor, A142 road]
-
A.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
hasNearbyDevelopmentCorridor
Indicates that an entity is located close to, or directly influenced by, a designated development corridor such as a planned or existing zone of concentrated growth or infrastructure.
-
C.
hasNearbyRailway
chosen
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
D.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
E.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.