Triple
T1791609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Zimbabwe |
E39507
|
entity |
| Predicate | importedGood |
P11260
|
FINISHED |
| Object | Chinese porcelain |
—
|
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: Chinese porcelain | Statement: [Great Zimbabwe, importedGood, Chinese porcelain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importedGood Context triple: [Great Zimbabwe, importedGood, Chinese porcelain]
-
A.
imported
chosen
Indicates that something was brought into a country, system, or context from an external source.
-
B.
customsInstrument
Indicates that one entity serves as a tool, method, or means used by customs authorities to perform or facilitate a customs-related action involving another entity.
-
C.
usedInInternationalTrade
Indicates that something participates as a good, service, or instrument in commercial exchanges between different countries.
-
D.
customs
Indicates that an entity is responsible for regulating, inspecting, or processing goods and people as they cross a border for legal and tax purposes.
-
E.
exportedTo
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.