Triple
T9068478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Open Knowledgebase (GOKb) collaboration |
E217302
|
entity |
| Predicate | dataCuration |
P37873
|
FINISHED |
| Object | community curation |
—
|
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: community curation | Statement: [Global Open Knowledgebase (GOKb) collaboration, dataCuration, community curation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCuration Context triple: [Global Open Knowledgebase (GOKb) collaboration, dataCuration, community curation]
-
A.
dataManagement
Indicates the relationship in which an entity organizes, stores, maintains, and governs data throughout its lifecycle.
-
B.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
C.
dataMaintained
chosen
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
dataContext
Indicates the situational or environmental conditions under which data is produced, interpreted, or used, such as source, scope, assumptions, and relevant constraints.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ba250819085fa49e0059d06c1 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.