Triple
T22036217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozelets |
E544214
|
entity |
| Predicate | tradingHistory |
P58558
|
FINISHED |
| Object | historically a local market town |
—
|
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: historically a local market town | Statement: [Kozelets, tradingHistory, historically a local market town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingHistory Context triple: [Kozelets, tradingHistory, historically a local market town]
-
A.
tradesUnderSymbol
Indicates that a financial instrument or security is listed and actively traded on a market using a specific ticker symbol.
-
B.
tradeItemsHistorically
chosen
Indicates that the entities have engaged in trading items with each other at some point in the past.
-
C.
historicalTradeDirection
Indicates the predominant directional flow of trade between entities during a specified historical period.
-
D.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
E.
storesHistory
Indicates that an entity retains or records past states, events, or changes over time related to another entity or process.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f1f95c8190a324c84313cd91ee |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.