Triple
T12325637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCORM |
E293821
|
entity |
| Predicate | conformanceLevel |
P65362
|
FINISHED |
| Object | SCORM-conformant content |
—
|
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: SCORM-conformant content | Statement: [SCORM, conformanceLevel, SCORM-conformant content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conformanceLevel Context triple: [SCORM, conformanceLevel, SCORM-conformant content]
-
A.
usesConformanceLevels
Indicates that one entity applies or adheres to defined conformance levels when interacting with or evaluating another entity.
-
B.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
C.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
D.
hasStandardizationLevel
chosen
Indicates the degree or extent to which something conforms to an established standard or set of standardized criteria.
-
E.
hasConformanceRequirements
Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.