Triple
T2073869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speicherstadt warehouse district |
E44876
|
entity |
| Predicate | historicallyStoredGoods |
P34774
|
FINISHED |
| Object | coffee |
—
|
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: coffee | Statement: [Speicherstadt warehouse district, historicallyStoredGoods, coffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyStoredGoods Context triple: [Speicherstadt warehouse district, historicallyStoredGoods, coffee]
-
A.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
B.
historicalExport
Indicates that an entity was exported from one place to another during a past or historically significant period.
-
C.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
-
D.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
E.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba101c008190840763d2f28fa8d7 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.