Triple
T28594359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Wikidata |
E723734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaboratively edited knowledge base |
C53127
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: collaboratively edited knowledge base Context triple: [Korean Wikidata, instanceOf, collaboratively edited knowledge base]
-
A.
federated wiki
A federated wiki is a decentralized, collaboratively edited web of interconnected pages where each user can host, fork, and modify content on their own server while still sharing and remixing it across the wider network.
-
B.
open knowledge organization
An open knowledge organization is a collaborative, transparent system for structuring, connecting, and sharing information that allows broad participation in creating, maintaining, and reusing knowledge resources.
-
C.
knowledge graph
chosen
A knowledge graph is a structured representation of entities and their relationships, typically modeled as nodes and edges, enabling machines to integrate, reason over, and derive insights from interconnected data.
-
D.
collaborative data science platform
A collaborative data science platform is an integrated environment where multiple users can jointly develop, run, and share data workflows, analyses, and models using shared datasets, tools, and computational resources.
-
E.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
- F. None of above.
Provenance (1 batch)
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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:21 a.m.