Triple
T8357418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golgi apparatus |
E196713
|
entity |
| Predicate | exportsCargoVia |
P82281
|
FINISHED |
| Object | transport vesicles |
—
|
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: transport vesicles | Statement: [Golgi apparatus, exportsCargoVia, transport vesicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportsCargoVia Context triple: [Golgi apparatus, exportsCargoVia, transport vesicles]
-
A.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
C.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
cargo
Indicates that one entity is the goods or load being transported, carried, or shipped by another entity.
- F. None of above. chosen
Provenance (4 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.