Triple
T18411604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Route 10 (proposed) |
E441770
|
entity |
| Predicate | crossBorderFunction |
P10963
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hong Kong Route 10 (proposed), crossBorderFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderFunction Context triple: [Hong Kong Route 10 (proposed), crossBorderFunction, yes]
-
A.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
B.
hasBorderCrossingFunction
chosen
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
C.
crossBorderPresence
Indicates that an entity maintains operations, activities, or influence that extend across national or jurisdictional borders.
-
D.
isCrossBorder
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
E.
crossBorderLinks
Indicates connections or interactions that extend across or link entities in different geographic or political jurisdictions.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a24e130819082b92f98d8d5fa3c |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.