Triple
T25288942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamrun |
E634025
|
entity |
| Predicate | tradeConnectedTo |
P23353
|
FINISHED |
| Object | interior of Persia |
—
|
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: interior of Persia | Statement: [Gamrun, tradeConnectedTo, interior of Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeConnectedTo Context triple: [Gamrun, tradeConnectedTo, interior of Persia]
-
A.
tradeNetwork
chosen
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
B.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading entity.
-
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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:21 p.m.