Triple
T26317747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nroff |
E662017
|
entity |
| Predicate | alternativeImplementation |
P162147
|
FINISHED |
| Object | GNU groff nroff |
—
|
NE NERFINISHED |
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: GNU groff nroff | Statement: [nroff, alternativeImplementation, GNU groff nroff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeImplementation Context triple: [nroff, alternativeImplementation, GNU groff nroff]
-
A.
alternativePlan
Indicates that one plan serves as a substitute or backup option for another plan within the same context or objective.
-
B.
alternativeRoute
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
C.
alternativeFlag
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
-
D.
alternativeLaunchMethod
Indicates that there exists a different or non-standard method by which the launch of something can be carried out.
-
E.
alternativeInstrumentation
Indicates that an entity uses a different or substitute set of instruments or instrumentation compared to a standard, primary, or original configuration.
- 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_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 26, 2026, 10:26 p.m.