Triple
T3770723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semper Augustus |
E82789
|
entity |
| Predicate | tradeParticipants |
P2823
|
FINISHED |
| Object | wealthy merchants |
—
|
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: wealthy merchants | Statement: [Semper Augustus, tradeParticipants, wealthy merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeParticipants Context triple: [Semper Augustus, tradeParticipants, wealthy merchants]
-
A.
tradingPartner
Indicates a relationship where two entities engage in the exchange of goods, services, or financial instruments with one another.
-
B.
hasMarketParticipants
chosen
Indicates that a market or trading venue involves or is associated with specific participating entities (such as buyers, sellers, or intermediaries).
-
C.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
D.
tradeNetwork
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
E.
sharesTradedFor
Indicates that shares of one entity are exchanged or traded in return for another asset, security, or form of consideration.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc307cf8819090730b5e697bb197 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.