Triple
T22135129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 638th Supply Chain Management Group |
E547004
|
entity |
| Predicate | typeOfLogistics |
P10774
|
FINISHED |
| Object | supply chain logistics |
—
|
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: supply chain logistics | Statement: [638th Supply Chain Management Group, typeOfLogistics, supply chain logistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLogistics Context triple: [638th Supply Chain Management Group, typeOfLogistics, supply chain logistics]
-
A.
logistics
chosen
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
B.
logisticsFeature
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
D.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
E.
usedLogisticsRoute
Indicates that a particular logistics route was employed to transport or move goods or resources between locations.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b9ee54819081141c4f28e1211a |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.