Triple
T26317739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nroff |
E662017
|
entity |
| Predicate | supportsLineLengthControl |
P196203
|
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, supportsLineLengthControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLineLengthControl Context triple: [nroff, supportsLineLengthControl, true]
-
A.
hasLineLength
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
B.
supportsLine
Indicates that one entity provides structural, functional, or conceptual backing or reinforcement to a particular line (such as a line of text, code, argument, or physical alignment).
-
C.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
D.
supportsLineSpacingAdjustment
Indicates that an entity provides functionality to modify or control the spacing between lines of text.
-
E.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
- 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_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 26, 2026, 10:26 p.m.