Triple
T6877888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian education system |
E158715
|
entity |
| Predicate | assessmentFeature |
P5048
|
FINISHED |
| Object | continuous assessment in compulsory school |
—
|
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: continuous assessment in compulsory school | Statement: [Norwegian education system, assessmentFeature, continuous assessment in compulsory school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessmentFeature Context triple: [Norwegian education system, assessmentFeature, continuous assessment in compulsory school]
-
A.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
B.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ccc29c8190904cb73c4cbb5dca |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.