Triple
T6554046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anqing |
E152399
|
entity |
| Predicate | hasRiverPortFunction |
P32300
|
FINISHED |
| Object | inland river port on the Yangtze |
—
|
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: inland river port on the Yangtze | Statement: [Anqing, hasRiverPortFunction, inland river port on the Yangtze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverPortFunction Context triple: [Anqing, hasRiverPortFunction, inland river port on the Yangtze]
-
A.
hasRiverPortStatus
chosen
Indicates that an entity holds the status of having a river port, meaning it is officially recognized as a location where river-based shipping or transport operations occur.
-
B.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
-
C.
hasRiverPortHistory
Indicates that an entity has a historical association with functioning as a river port or hosting river port activities.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.