Triple
T28389420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝天门 |
E719108
|
entity |
| Predicate | 交通属性 |
P55411
|
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.
transportationCharacteristic
chosen
Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
-
B.
typeOfTransportInfrastructure
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
C.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
D.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
E.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ceb933081909992f16507b0e667 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:12 a.m.