Triple
T17349921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Packhorse |
E421779
|
entity |
| Predicate | logisticsDomain |
P10774
|
FINISHED |
| Object | supply chain within the regiment |
—
|
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 within the regiment | Statement: [Packhorse, logisticsDomain, supply chain within the regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logisticsDomain Context triple: [Packhorse, logisticsDomain, supply chain within the regiment]
-
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.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for another entity.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2bd0a881909e71c89773d9273c |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.