Triple
T15631806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KOSDAQ Market |
E375831
|
entity |
| Predicate | hasListingBoard |
P119525
|
FINISHED |
| Object | main KOSDAQ board |
—
|
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: main KOSDAQ board | Statement: [KOSDAQ Market, hasListingBoard, main KOSDAQ board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingBoard Context triple: [KOSDAQ Market, hasListingBoard, main KOSDAQ board]
-
A.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
B.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
C.
hasServiceBoard
Indicates that an entity is associated with or connected to a specific service board, such as a panel or group responsible for providing or overseeing services.
-
D.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
E.
hasLocalBoards
Indicates that an entity is associated with one or more governing or administrative boards operating at a local or regional level.
- F. None of above. chosen
Provenance (4 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb536348190b93ed3c178d1ffb8 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.