Triple
T1837965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berezan Island |
E41108
|
entity |
| Predicate | wasTradingPostFor |
P12536
|
FINISHED |
| Object | Greek city-states |
—
|
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: Greek city-states | Statement: [Berezan Island, wasTradingPostFor, Greek city-states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTradingPostFor Context triple: [Berezan Island, wasTradingPostFor, Greek city-states]
-
A.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
B.
exclusiveTradingPostOf
Indicates a trading post that is dedicated to and used exclusively by a specific entity, with no other entities sharing its use.
-
C.
hasTrade
chosen
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
E.
exchangedFor
Indicates that one entity has been traded or substituted in return for 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.