Triple
T1693016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chongqing |
E36590
|
entity |
| Predicate | isUpperYangtzeShippingCenter |
P18124
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chongqing, isUpperYangtzeShippingCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpperYangtzeShippingCenter Context triple: [Chongqing, isUpperYangtzeShippingCenter, true]
-
A.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
B.
isInternationalWaterway
Indicates that a waterway is recognized as lying beyond the territorial jurisdiction of any single state and is subject to international navigation or legal regimes.
-
C.
firstChineseAntarcticStation
Indicates that the subject is the first Antarctic research station established by China.
-
D.
majorPortOnRiver
chosen
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
-
E.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.