Triple
T15885951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki Document 1992 |
E385192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CSCE summit document |
C36613
|
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: CSCE summit document Context triple: [Helsinki Document 1992, instanceOf, CSCE summit document]
-
A.
CSCE document
A CSCE document is an official record used in construction projects to capture, communicate, and track changes, clarifications, or supplemental instructions related to the scope, cost, or execution of the work.
-
B.
Emerging Security Challenges Division
The Emerging Security Challenges Division is a specialized organizational unit focused on identifying, analyzing, and addressing new and evolving threats—such as cyber, hybrid, technological, and non-traditional security risks—to inform policy, strategy, and operational responses.
-
C.
OSCE document corpus
A structured collection of documents related to Objective Structured Clinical Examinations (OSCE), including station checklists, scoring rubrics, case scenarios, and examiner guidelines, organized for reference, analysis, and educational use.
-
D.
W3C Technical Architecture Group finding
A W3C Technical Architecture Group finding is an authoritative document that articulates the TAG’s consensus guidance on architectural principles and best practices for the World Wide Web.
-
E.
United Nations outcome document
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
- F. None of above. chosen
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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.