Triple
T25239366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagri people |
E632419
|
entity |
| Predicate | transportOfGoods |
P91189
|
FINISHED |
| Object | traditional use of bullock carts |
—
|
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: traditional use of bullock carts | Statement: [Bagri people, transportOfGoods, traditional use of bullock carts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportOfGoods Context triple: [Bagri people, transportOfGoods, traditional use of bullock carts]
-
A.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
B.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
C.
commonlyTransportedIn
chosen
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
D.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for another entity.
-
E.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:07 p.m.