Triple
T24928447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNG |
E618924
|
entity |
| Predicate | hasChunkStructure |
P134317
|
FINISHED |
| Object | IHDR |
—
|
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: IHDR | Statement: [PNG, hasChunkStructure, IHDR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChunkStructure Context triple: [PNG, hasChunkStructure, IHDR]
-
A.
haveStructure
chosen
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
B.
hasChapterStructure
Indicates that one entity is organized into chapters or contains a defined chapter-based structure in relation to another entity.
-
C.
hasStructureCount
Indicates the number of structures associated with or contained by a given entity.
-
D.
hasStructureLevel
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
-
E.
hasOrderStructure
Indicates that there is a defined ordering relation imposed on the elements of a set or collection, specifying how they are arranged or compared in terms of order.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:29 a.m.