Triple
T12516797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | egrep |
E299208
|
entity |
| Predicate | POSIXRecommendation |
P34894
|
FINISHED |
| Object | use grep -E instead of egrep |
—
|
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: use grep -E instead of egrep | Statement: [egrep, POSIXRecommendation, use grep -E instead of egrep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: POSIXRecommendation Context triple: [egrep, POSIXRecommendation, use grep -E instead of egrep]
-
A.
recommendsUseOf
chosen
Indicates that one entity advises, endorses, or suggests the use of another entity as appropriate or beneficial in a given context.
-
B.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
C.
usedByOperatingSystems
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
D.
adoptedAsRecommendationBy
Indicates that something has been formally accepted and endorsed as a recommendation by a particular agent or authority.
-
E.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.