Triple
T29677269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G4 |
E750849
|
entity |
| Predicate | routeDesignationOf |
P167585
|
FINISHED |
| Object | Beijing–Hong Kong–Macau Expressway |
—
|
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: Beijing–Hong Kong–Macau Expressway | Statement: [G4, routeDesignationOf, Beijing–Hong Kong–Macau Expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeDesignationOf Context triple: [G4, routeDesignationOf, Beijing–Hong Kong–Macau Expressway]
-
A.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
B.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
auxiliaryRouteDesignation
Indicates that a route is designated as an auxiliary (e.g., spur, loop, bypass) of a primary route.
-
E.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6725e8c8c8190baf3a148eb6db098 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:08 p.m.