Triple
T36733837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kipkelion |
E907411
|
entity |
| Predicate | tradingRole |
P114890
|
FINISHED |
| Object | local market center |
—
|
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: local market center | Statement: [Kipkelion, tradingRole, local market center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingRole Context triple: [Kipkelion, tradingRole, local market center]
-
A.
majorTradeRole
Indicates that an entity plays a primary or highly significant role in trade activities or commercial exchange within a given context.
-
B.
typeOfTrading
chosen
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another entity.
-
C.
knownForTrading
Indicates that an entity is recognized or notable for engaging in trading activities, such as buying, selling, or exchanging goods, services, or assets.
-
D.
roleInFinance
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:12 p.m.