Triple
T26137015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoFood |
E659407
|
entity |
| Predicate | usesLogisticsNetwork |
P28699
|
FINISHED |
| Object | Gojek driver-partners |
—
|
NE NERFINISHED |
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: Gojek driver-partners | Statement: [GoFood, usesLogisticsNetwork, Gojek driver-partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLogisticsNetwork Context triple: [GoFood, usesLogisticsNetwork, Gojek driver-partners]
-
A.
usedLogisticsRoute
Indicates that a particular logistics route was employed to transport or move goods or resources between locations.
-
B.
logisticsFeature
chosen
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
C.
relevanceToLogistics
Indicates that something has significance, applicability, or impact within logistical processes, planning, or operations.
-
D.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
E.
logisticsConcept
Indicates a conceptual or categorical relationship where one entity represents, defines, or is classified as a logistics-related concept for 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 8:18 p.m.