Triple
T38373078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taicang Port |
E893542
|
entity |
| Predicate | supportsTradeDirection |
P204626
|
FINISHED |
| Object | imports |
—
|
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: imports | Statement: [Taicang Port, supportsTradeDirection, imports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTradeDirection Context triple: [Taicang Port, supportsTradeDirection, imports]
-
A.
supportsTradingType
Indicates that one entity enables, allows, or is compatible with a specified type or mode of trading.
-
B.
supportsTradingWith
Indicates that one entity enables, facilitates, or is in favor of conducting trade or commercial exchange with another entity.
-
C.
supportsShortSelling
Indicates that one entity enables, permits, or facilitates another entity engaging in short selling activities.
-
D.
historicalTradeDirection
Indicates the predominant directional flow of trade between entities during a specified historical period.
-
E.
supportsExchangeBetween
Indicates that one entity enables or facilitates the exchange or transfer of something (e.g., data, value, or resources) between two or more other entities.
- F. None of above. chosen
Provenance (4 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.