Triple
T31665397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XKRX |
E808110
|
entity |
| Predicate | relatedExchangeSegment |
P207487
|
FINISHED |
| Object | KOSPI |
E356386
|
NE 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: KOSPI | Statement: [XKRX, relatedExchangeSegment, KOSPI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedExchangeSegment Context triple: [XKRX, relatedExchangeSegment, KOSPI]
-
A.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
-
B.
associatedWithExchange
Indicates a relationship in which an entity is linked or connected to a particular exchange or trading platform.
-
C.
hasInterchangesWith
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
-
D.
exchangeSegmentOf
Indicates that one entity gives a portion or segment of something to another entity, typically as part of a reciprocal transfer or trade.
-
E.
exchangeSegment
Indicates a relationship where one entity trades or swaps a defined portion or segment of something with another entity.
- F. None of above. chosen
Provenance (5 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b84b2cb488190988609dd033dc33f |
completed | June 12, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:59 p.m.