Triple
T29635989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mwene Mutapa |
E755715
|
entity |
| Predicate | hasTradePartner |
P28668
|
FINISHED |
| Object | Portuguese traders |
—
|
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: Portuguese traders | Statement: [Mwene Mutapa, hasTradePartner, Portuguese traders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradePartner Context triple: [Mwene Mutapa, hasTradePartner, Portuguese traders]
-
A.
tradingPartner
chosen
Indicates a relationship where two entities engage in the exchange of goods, services, or financial instruments with one another.
-
B.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
hasTradePartnerRank
Indicates that an entity is assigned a specific rank or position within a hierarchy of trade partners.
-
E.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 28, 2026, 6:44 p.m.