Triple
T37637849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riga |
E936536
|
entity |
| Predicate | tradeLinkedTo |
P114590
|
FINISHED |
| Object | Polish–Lithuanian Commonwealth |
—
|
NE NERFINISHED |
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: Polish–Lithuanian Commonwealth | Statement: [Riga, tradeLinkedTo, Polish–Lithuanian Commonwealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeLinkedTo Context triple: [Riga, tradeLinkedTo, Polish–Lithuanian Commonwealth]
-
A.
tradeInvolves
Indicates that a trade or exchange relationship exists between the referenced entities, where goods, services, or value are transferred among them.
-
B.
tradedAlong
chosen
Indicates that an entity engaged in trade or exchange activities following or using a particular route, path, or corridor.
-
C.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
-
D.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
E.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.