Triple
T24813365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPEG 2000 |
E620848
|
entity |
| Predicate | definedInPart |
P157742
|
FINISHED |
| Object | ISO/IEC 15444-6 |
—
|
NE NERFINISHED |
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: ISO/IEC 15444-6 | Statement: [JPEG 2000, definedInPart, ISO/IEC 15444-6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInPart Context triple: [JPEG 2000, definedInPart, ISO/IEC 15444-6]
-
A.
definedInPart
chosen
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
B.
partlyDefinedBy
Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
-
C.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
D.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
E.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:56 a.m.