Triple
T29384839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sufa crossing |
E745222
|
entity |
| Predicate | typeOfGoodsHandled |
P5941
|
FINISHED |
| Object | construction materials |
—
|
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: construction materials | Statement: [Sufa crossing, typeOfGoodsHandled, construction materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGoodsHandled Context triple: [Sufa crossing, typeOfGoodsHandled, construction materials]
-
A.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
B.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
C.
hasCargoHandlingSpecialization
Indicates that an entity is specialized in handling specific types of cargo or cargo-handling operations.
-
D.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
E.
hasCargoHandlingMode
Indicates the method or procedure by which cargo is handled, loaded, or unloaded in a given context.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: April 28, 2026, 2:38 p.m.