Triple
T36907482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangshan Port |
E912816
|
entity |
| Predicate | cargoHandlingSpecialization |
P93658
|
FINISHED |
| Object | bulk cargo |
—
|
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: bulk cargo | Statement: [Tangshan Port, cargoHandlingSpecialization, bulk cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoHandlingSpecialization Context triple: [Tangshan Port, cargoHandlingSpecialization, bulk cargo]
-
A.
cargoSpecialization
chosen
Indicates that an entity is specialized or designated for handling, transporting, or managing a particular type or category of cargo.
-
B.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
C.
cargoOperations
Indicates the handling, movement, and management of cargo during loading, unloading, transfer, or storage activities.
-
D.
hasCargoHandlingMode
Indicates the method or procedure by which cargo is handled, loaded, or unloaded in a given context.
-
E.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdab70a0819089aa71d551e36612 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.