Triple
T23285261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 泰州 |
E588968
|
entity |
| Predicate | 著名水运 |
P14751
|
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.
waterTransport
chosen
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
B.
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.
-
C.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
D.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
-
E.
waterwayFunction
Indicates the primary role or purpose that a waterway serves, such as transportation, irrigation, drainage, or recreation.
- 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.