Triple
T13114489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundugumor society |
E311057
|
entity |
| Predicate | economicExchange |
P23727
|
FINISHED |
| Object | barter |
—
|
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: barter | Statement: [Mundugumor society, economicExchange, barter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicExchange Context triple: [Mundugumor society, economicExchange, barter]
-
A.
currencyOrEconomy
Indicates that there is a relationship involving the type, status, or characteristics of a currency or economic system associated with an entity.
-
B.
exchanges
chosen
Indicates a reciprocal transfer of something of value between two or more entities.
-
C.
tradeFocus
Indicates a primary emphasis on or specialization in a particular type of trade, transaction, or commercial activity within the relationship or context.
-
D.
economicBlock
Indicates a formal grouping of entities that coordinate or align their economic policies, trade, or financial activities as a unified bloc.
-
E.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98180b6ac8190ae5a1f7c1480bd54 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.