Triple
T38574703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perai, Penang |
E929367
|
entity |
| Predicate | roadNetworkNodeOf |
P18987
|
FINISHED |
| Object | Penang Bridge corridor |
—
|
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: Penang Bridge corridor | Statement: [Perai, Penang, roadNetworkNodeOf, Penang Bridge corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkNodeOf Context triple: [Perai, Penang, roadNetworkNodeOf, Penang Bridge corridor]
-
A.
roadNetworkHubOf
chosen
Indicates that one location functions as a central node or hub within the road network relative to another location or area.
-
B.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
C.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
D.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
E.
roadNetworkContext
Indicates the contextual relationship between elements within a road network, such as how roads, intersections, and related infrastructure are organized or interact.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.