Triple
T26317740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nroff |
E662017
|
entity |
| Predicate | supportsPageLengthControl |
P196239
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [nroff, supportsPageLengthControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPageLengthControl Context triple: [nroff, supportsPageLengthControl, true]
-
A.
supportsPagination
Indicates that the subject provides or is compatible with dividing content or results into discrete pages that can be navigated sequentially.
-
B.
supportsLineLengthControl
Indicates that an entity provides functionality to configure or enforce limits on the length of lines (e.g., in text or code).
-
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.
pageSize
Indicates the size or amount of content (such as items, records, or data) that is included or displayed on a single page.
-
E.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: April 26, 2026, 10:26 p.m.