Triple
T23285281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 泰州 |
E588968
|
entity |
| Predicate | 港口水系 |
P2432
|
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.
waterwaySystem
chosen
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
B.
primaryWaterways
Indicates that the related entities are connected through major or principal bodies of water, such as main rivers, canals, or shipping routes that serve as key waterways between them.
-
C.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
D.
isInlandWaterwayInfrastructure
Indicates that something is part of the physical facilities or structures used for inland waterway transport, such as canals, locks, or related navigational infrastructure.
-
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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964600888190b40ecbefdc8aec64 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:59 p.m.