Triple
T29010884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line Printer Daemon protocol |
E736561
|
entity |
| Predicate | supportsBannerPages |
P203892
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Line Printer Daemon protocol, supportsBannerPages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBannerPages Context triple: [Line Printer Daemon protocol, supportsBannerPages, yes]
-
A.
supportsPageCategories
Indicates that one entity provides functionality for handling or displaying categories associated with a page.
-
B.
usedBanner
Indicates that one entity employed or displayed another entity as a banner in some context or setting.
-
C.
supportsPagination
Indicates that the subject provides or is compatible with dividing content or results into discrete pages that can be navigated sequentially.
-
D.
supportsSubpages
Indicates that an entity is capable of having and managing subordinate or nested pages beneath it.
-
E.
supportsCustomCovers
Indicates that one entity provides the capability for another entity to use or define custom cover designs or images.
- F. None of above. chosen
Provenance (4 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_6a0245e83d5c8190b3cf9a5ea17c5d9c |
completed | May 11, 2026, 9:11 p.m. |
Created at: April 28, 2026, 9:42 a.m.