Triple
T11422024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68851 |
E270645
|
entity |
| Predicate | supportsPageSize |
P81188
|
FINISHED |
| Object | 4 KB |
—
|
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: 4 KB | Statement: [Motorola 68851, supportsPageSize, 4 KB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPageSize Context triple: [Motorola 68851, supportsPageSize, 4 KB]
-
A.
supportsPagination
Indicates that the subject provides or is compatible with dividing content or results into discrete pages that can be navigated sequentially.
-
B.
pageSize
chosen
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
C.
supportsNestedPaging
Indicates that one entity provides the capability for nested paging (second-level address translation) to be used by or within another entity.
-
D.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
E.
hasPage
Indicates that one entity includes, is associated with, or is documented by a specific page (such as a web page or document page).
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.