Triple
T15479228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Guatemala |
E376868
|
entity |
| Predicate | keyImport |
P118414
|
FINISHED |
| Object | manufactured goods |
—
|
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: manufactured goods | Statement: [Economy of Guatemala, keyImport, manufactured goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyImport Context triple: [Economy of Guatemala, keyImport, manufactured goods]
-
A.
keyExport
Indicates that a cryptographic key is transferred or made available from one system, location, or format to another.
-
B.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
C.
keyMaterial
Indicates that an entity serves as cryptographic key material used to secure, encrypt, or authenticate data in a security-related relationship.
-
D.
keyPair
Indicates a relationship where two cryptographic keys are associated as a matched pair, typically consisting of a public key and a corresponding private key used together for secure operations.
-
E.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8a77a081909f12f13660452f4a |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:34 a.m.