Triple
T23434785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G2 Beijing–Shanghai Expressway |
E563427
|
entity |
| Predicate | hasRouteCodePrefix |
P147043
|
FINISHED |
| Object | G |
—
|
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: G | Statement: [G2 Beijing–Shanghai Expressway, hasRouteCodePrefix, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteCodePrefix Context triple: [G2 Beijing–Shanghai Expressway, hasRouteCodePrefix, G]
-
A.
hasStationCodePrefix
Indicates that one entity’s station code begins with the prefix specified by the other entity.
-
B.
hasSiteCodePrefix
chosen
Indicates that one entity’s site code begins with, or is prefixed by, the specified code string from another entity.
-
C.
hasAirportCodePrefix
Indicates that an airport’s code begins with a specified sequence of characters.
-
D.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
E.
hasSuffixedRoute
Indicates that a route is a variant or extension of another base route, distinguished by an added suffix in its identifier.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5daabcc819094446a80723a487b |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.