Triple
T28711348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT |
E729838
|
entity |
| Predicate | scanLineStructure |
P138928
|
FINISHED |
| Object | two image channels interleaved in lines |
—
|
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: two image channels interleaved in lines | Statement: [APT, scanLineStructure, two image channels interleaved in lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanLineStructure Context triple: [APT, scanLineStructure, two image channels interleaved in lines]
-
A.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
B.
scanlinesPerFrame
chosen
Indicates the number of individual scanlines that are drawn or processed to compose a single frame.
-
C.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
D.
scanLineCorrectorIssue
Indicates that there is a problem or malfunction in the process or component responsible for correcting scan lines in an imaging or scanning system.
-
E.
loopLine
Indicates that a line or path forms a closed loop, returning to its starting point without interruption.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656d86d208190a537ece58e319ed4 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:48 a.m.