Triple
T26317800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | troff |
E662019
|
entity |
| Predicate | notableMacroPackage |
P86880
|
FINISHED |
| Object | -ms |
—
|
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: -ms | Statement: [troff, notableMacroPackage, -ms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMacroPackage Context triple: [troff, notableMacroPackage, -ms]
-
A.
notablePackage
chosen
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
-
B.
notableServicePack
Indicates that a particular service pack is especially significant or noteworthy in relation to the associated entity.
-
C.
notableExtension
Indicates that one entity is a significant or prominent extension, add-on, or expansion of another entity.
-
D.
notableRivalPackage
Indicates that one software package is recognized as a significant competitor or rival to another package.
-
E.
notableFramework
Indicates that an entity is a well-known or influential framework associated with another entity (such as a person, project, or organization).
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 26, 2026, 10:26 p.m.