Triple
T30150967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄浦江 |
E766392
|
entity |
| Predicate | 航运功能 |
P30340
|
FINISHED |
| Object | 通航内河船舶 |
—
|
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: 通航内河船舶 | Statement: [黄浦江, 航运功能, 通航内河船舶]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 航运功能 Context triple: [黄浦江, 航运功能, 通航内河船舶]
-
A.
maritimeFunction
Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
-
B.
shipFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
-
C.
waterwayFunction
chosen
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
-
D.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
E.
maritimeInfrastructure
Indicates the existence, presence, or involvement of facilities, structures, or systems that support maritime activities such as shipping, ports, and coastal operations between the related entities.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4297c81909062f19b7795f181 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.