Triple
T35185644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Brazil |
E1015976
|
entity |
| Predicate | importantColonialProduct |
P43018
|
FINISHED |
| Object | brazilwood |
—
|
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: brazilwood | Statement: [History of Brazil, importantColonialProduct, brazilwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantColonialProduct Context triple: [History of Brazil, importantColonialProduct, brazilwood]
-
A.
colonialExports
Indicates that one entity exports goods, resources, or products from a colony to another entity or destination.
-
B.
hasColonialEconomyBasedOn
chosen
Indicates that an entity’s colonial economy is primarily structured around or dependent on the specified resource, activity, or economic basis.
-
C.
belangrijkeKolonie
Indicates that one entity functioned as an important or significant colony of another entity.
-
D.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
E.
usedInColonialPeriod
Indicates that something was utilized or in active use during a historical colonial period.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.